PH09048: DURING TIBCO EMS SERVER FAILOVER, TRANSACTION ROLLBACK ISSUES MAY OCCUR THAT LEAD TO STUCK MESSAGES ON THE TIBCO QUEUE.

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When there is a failover of the Tibco JMS Provider, or
  connections get dropped and reconnected due to network issues,
  messages may be stuck in a delivered state on the Tibco queue.
   Once the failover completes or the connection is
  re-established, those messages don't get consumed by another
  transaction because they are in a delivered state.  Further
  processing of messages appears to be successful from the
  application's perspective but the receipt of the messages
  remains unacknowledged at the provider.
  
  This issue when the failover occurs is indicated in the
  SystemErr by the presence of a failure in XA end when calling
  the JMS Provider's XAResource:
  
  [2/19/19 12:58:17:042 EST]     FFDC
  Exception:javax.transaction.xa.XAException
  SourceId:com.ibm.ws.tx.jta.JTAXAResourceImpl.end ProbeId:307
  Reporter:com.ibm.ws.tx.jta.JTAXAResourceImpl@3d8400bc
  javax.transaction.xa.XAException
   at
  com.tibco.tibjms.TibjmsXAResource.buildXAException(TibjmsXAResou
  rce.java:805)
   at
  com.tibco.tibjms.TibjmsXAResource.buildXAException(TibjmsXAResou
  rce.java:783)
   at
  com.tibco.tibjms.TibjmsXAResource.endV2(TibjmsXAResource.java:31
  2)
   at
  com.tibco.tibjms.TibjmsXAResource.end(TibjmsXAResource.java:347)
   at
  com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.end(JMSManagedSe
  ssion.java:1407)
   at
  com.ibm.ejs.j2c.XATransactionWrapper.end(XATransactionWrapper.ja
  va:614)
   at
  com.ibm.ws.Transaction.JTA.JTAResourceBase.end(JTAResourceBase.j
  ava:254)
   at
  com.ibm.tx.jta.impl.RegisteredResources.sendEnd(RegisteredResour
  ces.java:1153)
   at
  com.ibm.tx.jta.impl.RegisteredResources.distributeEnd(Registered
  Resources.java:1129)
   at
  com.ibm.tx.jta.impl.TransactionImpl.distributeEnd(TransactionImp
  l.java:1770)
   at
  com.ibm.tx.jta.impl.TransactionImpl.prepareResources(Transaction
  Impl.java:1467)
   at
  com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing(Transac
  tionImpl.java:624)
   at
  com.ibm.tx.jta.impl.TransactionImpl.processCommit(TransactionImp
  l.java:1029)
   at
  com.ibm.tx.jta.impl.TransactionImpl.commit(TransactionImpl.java:
  963)
  ...
  
  The corresponding FFDC shows that the XAException received on
  the xa.end had error code XAER_NOTA
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of JMS   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Following a failover of the Tibco JMS   *
  *                      Provider requests to consume messages   *
  *                      fail.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This issue occurs due to an error in the WAS messaging code
  when the wrapper for the JMS managed Session processes
  XAExceptions in a particular code path that occurs when a
  Tibco EMS failover happens.
  This leaves the managed session in the wrong internal state
  which causes problems when the managed session is later reused
  to process subsequent messages.  Messages are still consumed
  from the JMS Provider, but the Session is not correctly
  enlisted with the JTA transaction.
  

Problem conclusion

• The error handling in the JMSManagedSession was corrected.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.16 and 9.0.5.0.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP