APAR status
Closed as program error.
Error description
This problem shows up when embedded messaging in installed.
When the startup of the application server is initiated, it
fails and the logs contain exceptions that say that broker
startup terminated unexpectedly.
.
■3/30/04 5:39:37:766 CST 3ebe2851 BrokerManager E MSGS0252E:
The Broker has terminated unexpectedly
and
■3/30/04 5:39:37:797 CST 3ebe2851 JMSService E MSGS0001E:
Starting the JMS Server failed with exception:
java.lang.Exception: MSGS0252E: The Broker has terminated
unexpectedly
at com.ibm.ws.messaging.BrokerManager.pingDFE
(BrokerManager.java:344)
at com.ibm.ws.messaging.BrokerManager.startFlows(BrokerManager.
java:808)
■3/30/04 5:39:37:812 CST 3ebe2851 ContainerImpl E WSVR0501E:
Error creating component null ■class
com.ibm.ws.messaging.JMSService
com.ibm.ws.exception.RuntimeWarning: MSGS0001E: Starting the JMS
Server failed with exception: java.lang.Exception: MSGS0252E:
The Broker has terminated unexpectedly
at
com.ibm.ws.messaging.JMSService.start(JMSService.java:295)
The preceding WSVR0501E is also logged in the systemout log.
.
This is cmvc defect 196504
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of Websphere Application Server *
* Embedded Messaging. *
****************************************************************
* PROBLEM DESCRIPTION: Problem occurs because the Replication *
* component does partial initialization *
* of transport parameters. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Two components in the application server, namely the embedded
messaging component and the replication component share the
same internal JMS provider as their transport. The replication
component sets some configuration parameters of the JMS
transport whether it is enabled or not. This causes the
embedded messaging component function to throw exceptions
when it tries to initialize the JMS provider. As a result,
the application server startup fails.
Problem conclusion
The replication component has been changed so that it no
longer sets configuration parameters of the JMS transport if
it has not been enabled. This fix will be made available in
the Application server cumulative fix 5.0.2.6 and 5.1.0.5.
Temporary fix Comments
APAR information |
APAR number |
PQ88448 |
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 |
2004-05-05 |
Closed date |
2004-05-26 |
Last modified date |
2004-06-11 |
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 |
R00W PSY |
UP |
|