PQ97281: JMSEXCEPTION MQJMS1068: FAILED TO OBTAIN XARESOURCE

APAR status
Closed as program error.

Error description
J2EE application sometimes fails to place mesage using JMS
into WebSphere MQ
Exceptions from application's log:
  2004-06-28 22:19:14,738 DEBUG  Thread-28  ipgw.mdb.
  IpgwMatchMDBClientBean sendNewBlockFile: got JMSException
   MQJMS1068:
  failed to obtain XAResource
  javax.jms.JMSException: MQJMS1068: failed to obtain XAResource
          at
  com.ibm.mq.jms.services.ConfigEnvironment.newException
  (ConfigEnvironment.java:540)
          at
  com.ibm.mq.jms.MQXAQueueConnection.createXAQueueSession
  (MQXAQueueConnection.java:96)
          at com.ibm.ejs.jms.mq.JMSWrapXAQueueConnection.
  internalCreateXAQueueSession(JMSWrapXAQueueConnection.java:309
)
          at
  com.ibm.ejs.jms.mq.JMSWrapXAQueueSession.createXASession
  (JMSWrapXAQueueSession.java:355)
  ...
The problem was triggered by "XA operation failed" error
(javax.transaction.xa.XAException) with error code -8
(which is XAER_DUPID, or duplicate XA id).
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users.      *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: Duplicate XID generated for JMS         *
*                                                              *
*                             resource.                        *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
*                                                              *
****************************************************************

Application Server uses identityHashCode to generate the unique
XID. When two objects return the same identityHashCode,
Application Server generates non-unique XIDs.
Problem conclusion
This fix replaces the use of identityHashCode to generate the
branch qualifies with a counter, which is incremeneted for
each resource taking part in transaction.
This fix is the equivalent of PQ96203 reported at WebSphere
Application Server Version 4.

The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.10 and 5.1.1.3 for WebSphere Application Server.
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 PQ97281
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-11-17
Closed date 2005-01-11
Last modified date 2006-04-26

APAR is sysrouted FROM one or more of the following:
PQ96203

APAR is sysrouted TO one or more of the following:

Modules/Macros
TRANIMPL          

Publications Referenced

Fix information

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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ97281
IBM Group: Software Group
Modified date: Apr 26, 2006