com.ibm.ws.exception.WsRuntimeException causes server startup failure
 Technote (troubleshooting)
 
Problem(Abstract)
com.ibm.ws.exception.WsRuntimeException due to a corrupt xml configuration file causes a server startup failure.
 
Cause
If the libraries.xml file does not load properly, it can result in this exception. If the libraries.xml file has been manually edited, there can be a carriage return after a line.

For example.


<libraries:Library xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:libraries="http://www.ibm.com/websphere/appserver/sch
emas/5.0/libraries.xmi" xmi:id="Library_1090521991016" name="wp522SharedLibrary">

In this case, the server does not start due to the carriage return after the appserver/sch.
This can happen with any corrupted xml files in the Install_Rroot /config directory. Manually editing the xml configuration files is not recommended.

Exception in SystemOut.log file

[8/31/04 12:01:53:963 CDT] 49cf9f WsServer E WSVR0003E: Server dmgr failed to start
com.ibm.ws.exception.WsRuntimeException
at com.ibm.ws.runtime.config.ResourceLocatorImpl.getResource(ResourceLocatorImpl.java:45at com.ibm.ws.runtime.component.LibraryMgrImpl.reload(LibraryMgrImpl.java:82)
at com.ibm.ws.runtime.component.LibraryMgrImpl.initialize(LibraryMgrImpl.java:49)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:706)

Exception in Trace.log file with *=all=enabled trace.
[8/31/04 12:01:53:953 CDT] 49cf9f ResourceLocat d /opt/Was5.0/DeploymentManager/config/cells/ProdNetwork/nodes/ProdManager/libraries.xml was not loaded
Wrapped exception
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
Attached SystemOut.log file and trace.log file contains the stack trace.

 
Resolving the problem
  1. Edit the server.xml file for the dmgr located in Install_Root /config/cells/cellname/nodes/nodename/servers/servername directory.

  2. Find the TraceService xml tag section.

  3. Modify the startupTraceSpecification entry to look like this:

    *=all=enabled

  4. Make sure enable is set to true.

  5. Start the server.

  6. Edit the Install_Root /logs/trace.log file and search for exception.

  7. Look for the failing xml file. In the above example: libraries.xml was not loaded.

  8. Edit the corrupted xml file and make the necessary changes.

  9. Restart the server.
 
SystemOut.logtrace.log
 
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 > System Management/Repository
Operating system(s): Windows
Software version: 5.0.2.7
Software edition:
Reference #: 1179011
IBM Group: Software Group
Modified date: Sep 9, 2004