APAR status
Closed as program error.
Error description
After the following error messages appear in the WebSphere
Application Server system log :
XATransaction E J2CA0030E: Method enlist caught
javax.transaction.SystemException: Failed to start the
transaction association.
at
com.ibm.ejs.jts.jta.TransactionImpl.enlistResource(TransactionIm
pl.java(Compiled Code))
at com.ibm.ejs.jts.jta.JTSXA.enlist(JTSXA.java(Compiled Code))
...
while trying to enlist resources from datasource < queue
connection factory> with the Transaction Manager for the current
transaction, and threw a ResourceException.
ConnectionEve A J2CA0056I: The Connection Manager received a
fatal connection error from the Resource Adaptor for resource
<nam>. The exception which was received is
javax.jms.JMSException: Enlist failed
ExceptionUtil E CNTR0020E: Non-application exception occurred
while processing method "onMessage" on bean <message driven
bean>. Exception data:
java.lang.reflect.InvocationTargetException:
javax.jms.JMSException: Enlist failed
at
com.ibm.ejs.jms.JMSCMUtils.mapToJMSException(JMSCMUtils.java(Com
piled Code))
at
com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java(
Compiled Code))
the message-driven beans (MDBs) named in the errors stop
receiving messages.
Occassionally, following this error, the application server will
hang when shutting down.
This problem only occurs if the MDBs named in the errors are
using Listener Ports that have their Maximum sessions property
set to a value greater than 1. APAR
PK00582 describes a problem
with similar symptoms - however, that APAR only applies if
the Maximum sessions property for the Listener Port is set to
the value 1.
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: After the following error messages *
* appear in the WebSphere Application *
* Server system log : *
* *
* J2CA0030E: Method enlist caught *
* javax.transaction.SystemException: *
* Failed to start the transaction *
* association. *
* at com.ibm.ejs.jts.jta. *
* TransactionImpl.enlistResource *
* (TransactionIm pl.java(Compiled *
* Code)) *
* at com.ibm.ejs.jts.jta.JTSXA.enlist *
* (JTSXA.java(Compiled Code)) *
* ... *
* *
* while trying to enlist resources from *
* datasource <queue connection factory> *
* with the Transaction Manager for the *
* current transaction, and threw a *
* ResourceException. *
* *
* 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, *
* and the application server hangs when *
* shutting down. *
* *
* This problem only occurs if the MDBs *
* named in the errors are using *
* Listener Ports that have their *
* Maximum sessions property set to a *
* value greater than 1. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the Enlist error occurs, a deadlock is reached as we
have multiple Server Sessions blocked on a Connection Handle
object that is in use by the first Session that detected the
error - however, this first Server Session is blocked as it
is waiting for the other Sessions to finish processing the
error.
Problem conclusion
The application server's Server Session Pool has been
rewritten to prevent the deadlock condition from being
reached.
The fix for this APAR is currently targeted for inclusion
in Cumulative Fix 11 for WebSphere Application Server Version
5.0.2, Cumulative Fix 4 for WebSphere Application Server
Version 5.1.1 and Cumulative Fix 3 for WebSphere Application
Server Version 6.0.0. Please refer to the Recommended Updates
page for delivery dates:
http://www-1.ibm.com/support/
docview.wss?rs=180&context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK01477 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-22 |
Closed date |
2005-03-09 |
Last modified date |
2005-03-09 |
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 |
|