|
Problem(Abstract) |
If someone accidentally clicks Apply in the "Message
Listener Service" for the jmsserver, then saves the changes, the
jmsserver's configuration is corrupted and does not start. |
|
|
|
Cause |
If the following occurs with the jmsserver configuration
in the Administrative Console, the configuration becomes corrupt, causing
the jmsserver to not start. The steps that cause the corruption are as
follows:
The corruption is contained in a single jmsserver file called server.xml.
This is located in the WAS_HOME/config/cells/cell
name/nodes/node name/servers/jmsserver directory. |
|
|
Resolving the
problem |
Clean up
In the Network Deployment Manager installation, in the server.xml file,
manually remove the section between:
<services xmi:type="applicationserver:TransactionService"
xmi:id="TransactionService_1" enable="true"
totalTranLifetimeTimeout="120" clientInactivityTimeout=
"60"/>
and
<components xmi:type="applicationserver.webcontainer:
WebContainer" xmi:id="WebContainer_1" enableServletCaching
="true">
Remove the following entries:
<services xmi:type="applicationserver.ejbcontainer.
messagelistener:MessageListenerService" xmi:id=
"MessageListenerService_1075783769874" enable="true"/>
After you save your changes to the Network Deployment Manager config/cells
directory, do a Full Resynchronization to properly correct this issue.
Fix
Apply the WebSphere 5.0.2.4 Cumulative Fix to avoid this problem in the
future. If the jmsserver is already corrupt, follow the steps under
Clean up to repair WebSphere Application Server.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|