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.
|