APAR status
Closed as program error.
Error description
After the following error messages appear in the WebSphere
Application Server system log:
ConnectionEve A J2CA0056I: The Connection Manager received a
fatal connection error from the Resource Adaptor for
resource <name>. The exception which was received is
javax.jms.JMSException: Enlist failed
the Message Driven Beans (MDBs) named in the errors stop
receiving messages. However, the listener port associated with
the MDB is still running.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the *
* Java Message Service (JMS) functionality *
* provided with WebSphere Application Server *
* Version 5.x. *
****************************************************************
* PROBLEM DESCRIPTION: When the Application Server attempts *
* to deliver a message to a Message *
* Driven Bean, the following errors *
* occur: *
* *
* J2CA0030E: Method enlist caught *
* javax.transaction.SystemException: *
* Failed to start the transaction *
* association. *
* J2CA0056I: The Connection Manager *
* received a fatal connection error *
* from the Resource Adaptor for *
* resource <resource reference>. *
* The exception which was received is *
* javax.jms.JMSException: Enlist failed *
* CNTR0020E: Non-application exception *
* occurred while processing method *
* "onMessage" on bean <MDB name>. *
* Exception data: *
* java.lang.reflect. *
* InvocationTargetException: *
* javax.jms.JMSException: Enlist failed *
* *
* Once the exceptions have occurred, the *
* MDB mentioned in the errors never *
* processes any further message. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the Enlist error occurs, the JMS connection is shut down.
However, the Exception Listener for the Message Driven Bean
(MDB) that is using the connection is never notified. As far
as the MDB is concerned, the connection is still valid.
Problem conclusion
The JMS Connection code has been changed to notify the Message
Driven Bean (MDB) Exception Listener when an Enlist error
occurs. This results in the Listner Port that associated with
the MDB to shut down, and restart, which reestablishes the
JMS connection.
Temporary fix Comments
APAR information |
APAR number |
PQ82637 |
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-12-24 |
Closed date |
2004-01-13 |
Last modified date |
2004-01-13 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PQ97251
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 |
|