|
Problem(Abstract) |
Server fails to start due to corrupted resources.xml
file. |
|
|
|
Cause |
The following exceptions are thrown in the SystemOut.log
file while starting the IBM® WebSphere® Application Server.
[5/24/06 11:27:08:446 EDT] 26bbe594 ConfigError I WSVR0300I: Problems
found in
d:\apps\WebSphere\AppServer\config/cells/cr2rchgap02e/nodes/cr2rchgap02e\resources.xml
[5/24/06 11:27:08:462 EDT] 26bbe594 ConfigError W WSVR0307W: Invalid
namespace, resources.jms.internalmessaging, at line 7
[5/24/06 11:27:08:478 EDT] 26bbe594 ConfigError W WSVR0303W: Invalid
element tagname, connectionPool, at line 8
[5/24/06 11:27:08:478 EDT] 26bbe594 ConfigError W WSVR0303W: Invalid
element tagname, sessionPool, at line 9
[5/24/06 11:27:08:493 EDT] 26bbe594 ConfigError W WSVR0307W: Invalid
namespace, resources.jms.internalmessaging, at line 11
[5/24/06 11:27:14:290 EDT] 26bbe594 WsServer E WSVR0003E: Server server1
failed to start
java.lang.NullPointerException at
com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:519)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:413)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:362)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:117
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[5/24/06 11:27:14:431 EDT] 26bbe594 WsServer E WSVR0009E: Error occurred
during startup
WSVR0303W Warning message is the root cause of the problem. The
NullPointerException is thrown, just because the resource haspmap values
are empty.
The resources.xml file under the node is corrupted. If we compare the file
with any other working environment we may not see any difference in any
line. |
|
|
Resolving the
problem |
There are two ways to workaround the problem.
Option 1 :
- Move the
install-root/config/cells/cellName/nodes/nodeName/resources.xml file to
temp location.
- Move the
install-root/bin/wsinstance/configdefaults/cells/cellName/nodes/nodeName/
resources.xml to install-root/config/cells/cellName/nodes/nodeName.
- Start the server again.
- If the server fails to start with same exception, it means
both the resources.xml are corrupted.
- If it starts then it is user responsibility to create all
the node level resources (if it was created before the corruption) like
JDBC resources , mail resources .
Option 2 :
- Move the
install-root/config/cells/cellName/nodes/nodeName/resources.xml file to
temp location.
- Copy the resources.xml file from any other working
environment and then place it under the nodes folder. Make sure both the
versions are same Application Server version. If you don't have any other
working environment with same version, then it is user responsibility to
compare all the lines in the resources.xml of working and non working
System and then modify the file accordingly.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Historical Number |
71059
019
000 |
|
|
|
|