|
Problem(Abstract) |
The Node Agent does not start the application servers if
it cannot perform the synchronization successfully when Startup
auto-synchronization of the nodeagent is enabled. A NullPointerException
is seen in the nodeagent SystemOut.log file during nodeagent startup. |
|
Symptom |
If the Node restart state in the server monitoring policy
is set to running and the Startup Synchronization is set to true in the
nodeagent System Administration, the following exception is seen in the
nodeagent SystemOut.log file during nodeagent startup. The nodeagent also
fails to start the server.
12/14/04 11:43:29:253 EST] 28680f95 NodeSync E ADMS0012E: Unable to create
administrative client connection:
com.ibm.websphere.management.exception.AdminException: Admin client
connection to deployment manager is unavailable
at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:484)
at
com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:344)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:220)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:139)
at java.lang.Thread.run(Thread.java:567)
Caused by: java.lang.NullPointerException
Refer to the attached Nodeagent SystemOut.log file.
|
|
Resolving the
problem |
The Node Agent does not start the application servers if
it cannot perform the synchronization successfully when Startup
auto-synchronization of nodeagent is enabled. This behavior is working as
designed.
To avoid the exception in the nodeagent SystemOut.log file:
- Uncheck the Startup Synchronization in System
Administration > Node Agents > node_agent_name > File
Synchronization Service.
or
- Change the Node restart state to stopped in Servers >
Application Servers > server_name > Process Definition > process
type > Monitoring Policy.
|
|