PM41284: SOME ADAPTER EVENTS WILL BE LOST DUE TO PROBLEMS DURING TRANSACTION COMPLETION.

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• In a global transaction scenario which includes inbound(sync
  mode) and outbound, some events will be lost after
  starting/stopping app frequently.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application Server
  ****************************************************************
  * PROBLEM DESCRIPTION: IllegalStateException or                *
  *                      SystemException thrown during           *
  *                      completion phase of transaction         *
  *                      processing.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is caused by multi-threading issues that result
  from attempting to rollback a transaction while shutting down
  a resource performing transacted message delivery on one
  thread, while attempting to commit the transaction as part of
  transaction recovery processing on another thread.  This issue
  can result in either :
  
  (1) a SystemException thrown with a stack similar to :
  javax.transaction.SystemException
   at
  com.ibm.tx.jta.TransactionState.setState(TransactionState.java:6
  05)
   at
  com.ibm.tx.jta.TransactionImpl.prepareResources(TransactionImpl.
  java:1482)
   at
  com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing(Transac
  tionImpl.java:552)
   at
  com.ibm.tx.jta.TransactionImpl.processCommit(TransactionImpl.jav
  a:983)
   at
  com.ibm.tx.jta.TransactionImpl.commit(TransactionImpl.java:918)
   at
  com.ibm.ws.tx.jta.TranManagerImpl.commit(TranManagerImpl.java:37
  7)
   at
  com.ibm.tx.jta.TranManagerSet.commit(TranManagerSet.java:161)
  ..
  
  (2) or a IllegalStateException thrown with a stack similar to :
  java.lang.IllegalStateException: transactionComplete: illegal
  state exception. State = STATE_INACTIVE
   at
  com.ibm.ejs.j2c.MCWrapper.transactionComplete(MCWrapper.java:137
  5)
   at
  com.ibm.ejs.j2c.XATransactionWrapper.afterCompletion(XATransacti
  onWrapper.java:357)
   at
  com.ibm.tx.jta.RegisteredSyncs.coreDistributeAfter(RegisteredSyn
  cs.java:357)
   at
  com.ibm.ws.tx.jta.RegisteredSyncs.distributeAfter(RegisteredSync
  s.java:317)
   at
  com.ibm.tx.jta.TransactionImpl.distributeAfter(TransactionImpl.j
  ava:2933)
   at
  com.ibm.tx.jta.TransactionImpl.postCompletion(TransactionImpl.ja
  va:2892)
   at
  com.ibm.tx.jta.TransactionImpl.postCompletion(TransactionImpl.ja
  va:2805)
   at
  com.ibm.tx.jta.TransactionImpl.recoverRollback(TransactionImpl.j
  ava:2153)
   at
  com.ibm.ws.tx.jta.TxExecutionContextHandler.stoppingProvider(TxE
  xecutionContextHandler.java:209)
   at
  com.ibm.ws.tx.jta.TranManagerSet.stoppingProvider(TranManagerSet
  .java:453)
  ..
  
  during various stages of transaction completion processing.
  

Problem conclusion

• Rather than attempting to rollback the transaction, mark the
  transaction for rollback only.  This prevents any conflict in
  the transaction completion processing.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.21.  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

• R700 PSY

     UP