Nodeagent fails to start with WSVR0003E exception
 Technote (troubleshooting)
 
Problem(Abstract)
Due to a power failure or any unexpected interruption, the monitor.state file in the nodeagent logs folder may be corrupted and this may cause a nodeagent start issue.
 
Cause
Nodeagent fails to start after power outage with the following exception.


[23/08/06 19:33:28:374 EST] 11a9310 WsServer E WSVR0003E: Server
nodeagent failed to start
com.ibm.ws.exception.RuntimeError at
com.ibm.ws.management.component.NodeAgentImpl.start(NodeAgentImpl.java:103) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2) at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1444)
at com.ibm.ws.management.nodeagent.NodeAgent.loadNodeState(NodeAgent.java:1890) at com.ibm.ws.management.nodeagent.NodeAgent.loadMonitoringPolicies(NodeAgent.java:1651)
at com.ibm.ws.management.nodeagent.NodeAgent.initialize(NodeAgent.java:278)
at com.ibm.ws.management.nodeagent.Forwarder.initReceiver(Forwarder.java:31) at com.ibm.ws.management.component.NodeAgentImpl.registerAgentMBean(NodeAgentImpl.java:274)
at com.ibm.ws.management.component.NodeAgentImpl.start(NodeAgentImpl.java:89)


Nodeagent stores the application server monitoring policy information in the monitor.state file. Due to a power failure or any unexpected interruption like a crash , the monitor.state file may get corrupted or the information in the monitor.state file may be lost and cause an issue with the start of nodeagent.

 
Resolving the problem
To resolve the problem, remove all the log files under install-root/logs/nodeagent including monitor.state file and then start the nodeagent server.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
51556
999
616
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1246402
IBM Group: Software Group
Modified date: Sep 22, 2006