|
Problem(Abstract) |
Node synchronization could fail after an application is
installed or removed from an IBM® WebSphere® Application Server V5.0
Network Deployment configuration. This problem can result from a
configuration save conflict.
Synchronization Error from NodeAgent SystemOut.log
[12/9/04 5:26:21:903 EST] 14e97543 NodeSyncTask A ADMS0016I: Configuration
synchronization failed.
[12/9/04 5:27:21:865 EST] 14eb3543 NodeSync E ADMS0005E: Unable to
generate synchronization request: javax.management.RuntimeMBeanException
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java(Compiled
Code))
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java(Compiled
Code))
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java(Compiled
Code))
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java(Compiled
Code))
at $Proxy0.invoke(Unknown Source)(Compiled Code)
at
com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java(Inlined
Compiled Code))
at
com.ibm.ws.management.sync.NodeSync.invokeGetModifiedFolders(NodeSync.java(Compiled
Code))
at
com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java(Compiled
Code))
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java(Compiled
Code))
at java.lang.Thread.run(Thread.java(Compiled Code))
---- Begin backtrace for nested exception
java.lang.NullPointerException |
|
|
|
Cause |
This failure can result from a mismatch of the
serverindex.xml file that lists which applications are
installed on individual servers on a node, and the Applications folder
that stores the application
deployment information. This mismatch can result from a configuration save
conflict. |
|
|
Resolving the
problem |
If synchronization of your V5.0 environment fails
following an application installation or update, perform the following
steps to troubleshoot:
- Open the Install_Root\DeploymentManager\config\cells\<cell
name>\nodes\<node name>\serverindex.xml file. Open the
serverindex.xml file for each node. Verify that these files are being
opened from the Network Deployment node, because the master repository is
stored on this node.
- Check the following file to see which applications have been deployed.
Example:
<deployedApplications>DefaultApplication.ear/deployments/DefaultApplication</deployedApplications>
It can be helpful to extract each line containing the
"<deployedApplications>" XML tag and move them to another file to
make the next step easier.
- Every application listed in each serverindex.xml file must have a
corresponding directory under the
Install_Root\DeploymentManager\config\cells\<cell
name>\applications folder. A folder with the same name as the
application is located there. This list of applications is also the list
that is displayed in the Network Deployment administrative console.
- Check each deployed application from step #2 and make sure that it has
an application folder from step 3.
Following the previous steps, you might discover that the serverindex.xml
file has an application that does not have a corresponding folder under
the applications directory. It is assumed that because the application
does not have an Applications folder that it has been removed and is no
longer needed in the configuration. To correct the synchronization, delete
any entries in the serverindex.xml file for these applications.
For example, the application DefaultApplication.ear file is shown
in the following serverindex.xml file, but does not have a corresponding
Install_Root\DeploymentManager\config\cells\<cell
name>\applications\DefaultApplication.ear directory.
Before
<serverEntries xmi:id="ServerEntry_1073580257067"
serverDisplayName="server1" serverName="server1"
serverType="APPLICATION_SERVER">
<deployedApplications>Monitor.ear/deployments/Monitor</deployedApplications><deployedApplications>DefaultApplication.ear/deployments/Monitor</deploye
dApplications>
<specialEndpoints
xmi:id="NamedEndPoint_1073580257067"endPointName="BOOTSTRAP_ADDRESS">
After
<serverEntries xmi:id="ServerEntry_1073580257067"
serverDisplayName="server1" serverName="server1"
serverType="APPLICATION_SERVER">
<deployedApplications>Monitor.ear/deployments/Monitor</deployedApplications>
<specialEndpoints
xmi:id="NamedEndPoint_1073580257067"endPointName="BOOTSTRAP_ADDRESS">
- After this file is corrected, run a full synchronization from the
Network Deployment administrative console. If this synchronization fails,
stop the node agent and run the syncNode.sh file from the
Node_Install_Root/bin directory. Be sure to use the correct SOAP
port and security user ID and password, if security is enabled.
If problems continue, run the Install_Root/bin/collector.sh file
for Network Deployment and all the nodes and send them to your support
representative after a PMR has been opened.
What is the cause of this problem?
Example:
If two administrators, admin1 and admin2, both log into the
Network Deployment administrative console, they each get their own copies
of the administrative repository as it currently exists. If admin1 deletes
the DefaultApplication.ear file , this action updates the admin1
serverindex.xml file as well as deleting the Applications folder for this
application. If admin1 then saves these changes, the master repository is
updated and the DefaultApplication.ear file is removed.
If admin2, does not make changes and saves the configuration, a problem
can occur because admin2 got the version of the repository prior to the
removal of the default application. If admin2 tries to save this
configuration, a pop-up message warning displays indicating that some
configuration change has occurred and asking whether or not to continue
the save. If admin2 continues with the save, the master repository is
updated with the admin2 serverindex.xml file. This action produces the
previous problem where the serverindex.xml file has an application listed,
but this application has no folder in the master configuration because it
was removed.
To avoid this situation:
- Limit the number of administrators that can install and uninstall
applications.
- Be attentive to the save conflict messages and follow up with other
administrators who might have also been logged into the administrative
console.
- Coordinate installation and removal of applications between
administrators to ensure that no save conflicts occur. Designate specific
time periods when administrators can perform administrative actions.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|