APAR status
Closed as program error.
Error description
node agent fails to restart appservers if startup sync for
nodeagent is enabled.
Some of the error messages you will see are:
ADMN1000I: Attemptmade to launch servername ... node ...
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)
.
.
.
ADMS0016I: Configuration synchronization failed.
.
.
.
---- Begin backtrace for nested exception
java.lang.NullPointerException
With the NodeAgent and JVMs stopped, when restarting the
NodeAgent, the JVM's do not come back up.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users with *
* Startup Synchronization for NodeAgent *
* enabled *
****************************************************************
* PROBLEM DESCRIPTION: When users start the Node Agent the *
* servers are not getting started even *
* if you set Monitoring policy as Running *
* for servers. But this is not consistent *
* behaviour.Sometimes servers are started *
* and sometimes they are not started. *
* *
* Application Servers > server1 > *
* Process Definition->MonitoringPolicy *
* set as Running *
* *
* This problem only occurs if *
* Startup Synchronization is Enabled *
* for the node *
* Node agents > NodeAgent Server -> *
* File Synchronization Service *
* Startup Synchronization is Enabled *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This problem only occurs if Startup Synchronization is Enabled
for the node
Node agents > NodeAgent Server -> File Synchronization Service
Startup Synchronization is Enabled
1) Goto Administrative Console
2) Application Servers > server1 > Process Definition->
MonitoringPolicy
set as Running
3) Node agents > NodeAgent Server -> File Synchronization
Service
Startup Synchronization is Enabled
4) Start Node Agent
5) If you execute ServerStatus -all then you see that servers
are not started.
Problem conclusion
Code has been corrected so that this problem is solved.
The fix for this APAR is currently targeted for
inclusion in fixpack 5.0.2.11 and 5.1.1.4 Please refer to the
Recommended Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=
180&context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ99359 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
103 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-01-11 |
Closed date |
2005-03-08 |
Last modified date |
2005-03-08 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|