Node discovery fails and stops synchronization with a java.lang.NullPointerException
 Technote (troubleshooting)
 
Problem(Abstract)
The nodeagent discover port is not listening on the machine; therefore, no servers are discovered and synchronization fails with a java.lang.NullPointerException.
 
Cause
A discovery trace on the nodeagent can help determine the cause of the problem. The following trace string traces the discovery process:

com.ibm.ws.management.*=all=enabled
[9/9/03 11:09:08:785 CDT] 4237aec3 JMXConnectors d Got Exception initializing discovery: java.lang.NullPointerException
at com.ibm.ws.management.component.
JMXConnectors$EndPtCollector.
<init>(JMXConnectors.java:957)

at com.ibm.ws.management.component.JMXConnectors.
initDiscovery(JMXConnectors.java:195)

at com.ibm.ws.management.component.JMXConnectors.
propertyChange(JMXConnectors.java:1203)

at java.beans.PropertyChangeSupport.firePropertyChange
(PropertyChangeSupport.java:244)
at java.beans.PropertyChangeSupport.firePropertyChange
(PropertyChangeSupport.java:171)
at com.ibm.ws.runtime.component.ComponentImpl.setState
(ComponentImpl.java:115)
at com.ibm.ws.runtime.component.ComponentImpl.setStartState
(ComponentImpl.java:132)
at com.ibm.ws.runtime.component.ServerImpl.start
(ServerImpl.java:188
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)


Because of this error, the discover process is not completely initialized, causing the synchronization to fail.
 
Resolving the problem
Above this error is the following trace output:

[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing server: server1

[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing endPoint: CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS
[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing endPoint: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS
[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing endPoint: SAS_SSL_SERVERAUTH_LISTENER_ADDRESS
[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing endPoint: DRS_CLIENT_ADDRESS
[9/9/03 11:09:08:473 CDT] 4237aec3 JMXConnectors d processing endPoint: SOAP_CONNECTOR_ADDRESS
[9/9/03 11:09:08:770 CDT] 4237aec3 JmxDM > ffdcDumpDefaultJmx
[9/9/03 11:09:08:770 CDT] 4237aec3 AdminDiagnost > defaultDump
[9/9/03 11:09:08:785 CDT] 4237aec3 AdminDiagnost < defaultDump
[9/9/03 11:09:08:785 CDT] 4237aec3 JmxDM < ffdcDumpDefaultJmx

The processing server, server1, is the cause of the NullPointerException. Something about server1 is corrupted, either the SOAP_CONNECTOR_ADDRESS in the serverindex.xml file or the server.xml file is missing from the $WAS_HOME/config/cells/cell name/nodes/node name/server/server1 directory.

If you cannot determine what is wrong, call 800-IBM-SERV, open a problem management record (PMR), then send your I/config/cells directory and the discovery trace to weblev2@us.ibm.com.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1162420
IBM Group: Software Group
Modified date: Apr 21, 2006