APAR status
Closed as program error.
Error description
The admin console can corrupt the server.xml for the JMs server
when you go to servers => JMS Servers => jmsserver => Server
Components => Application Server => Message Listener Service
and press "Apply". This screen is blank and once you press
Apply it shows some setting and now the server.xml is corrupted.
Local fix
Clean the server.xml or place an old copy.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Network *
* Deployment users using Administration *
* Console to configure JMS Server Message *
* Listener Service. *
****************************************************************
* PROBLEM DESCRIPTION: The jmsserver cannot start after the *
* following actions are performed in *
* Administration Console: *
* Go to *
* Servers => JMS Servers => jmsserver => *
* Server Components => Application Server *
* => Message Listener Service => Apply *
* *
* There is also the following exception *
* in SystemOut.log for jmsserver: *
* Server jmsserver failed to start *
* com.ibm.ws.exception.ConfigurationError *
* :MessageListenerService - no thread *
* pool defined. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The incomplete configuration will be saved to server.xml
which caused the exception in the SystemOut.log. In fact,
the Admin Console should not allow users to configure the
Server Components property for the JMS Server in an ND
environment. When using ND, the JMS Server is a separate
application server that has a single purpose - to provide
access to the JMS resources in the ND domain. It doesn't
make sense to configure additional server components, such
as a name server or application server, particularly as
applications cannot be installed into the JMS Server.
Problem conclusion
The Server Component link has been removed from the page
where jmsserver is configured.
Temporary fix
PQ78797_Test.jar
Comments
Special Instruction for PQ78797 Test Fix
1. Prerequisite
Please upgrade to WAS Cumulative Fix 5.0.2.3 before applying
this fix. This test fix should be removed after 5.0.2.4 is
available. 5.0.2.4 will contain the official fix for PQ78797.
2.Manual steps
If your jmsserver could not start and you had performed the
following in Admin Console:
Click Servers->JMS Servers->jmsserver->Server Components->
Application Server->
Message Listener Service->Apply->Save, you need to clean up
the jmsserver\server.xml
before applying this fix. For example, on windows, the location
of jmsserver\server.xml is
<Drive>:\WebSphere5\DeploymentManager\config\cells\myNetwork\
nodes\mynode\servers\jmsserver\server.xml.
In server.xml, 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">
You will find some entries like the following that should be
removed:
<services xmi:type="applicationserver.ejbcontainer.
messagelistener:MessageListenerService" xmi:id=
"MessageListenerService_1075783769874" enable="true"/>
Stop dmgr and node.
Applying PQ78797.
Start dmgr and node.
3. This fix essentially disables the configuration for Server
Components under jmsserver but it will not clean up the
corrupted server.xml.
APAR information |
APAR number |
PQ78797 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-09-23 |
Closed date |
2004-02-13 |
Last modified date |
2004-02-13 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|