PK41846: ILLEGALSTATEEXCEPTION DUE TO EXTENDEDJTATRANSACTION SYNCHRONIZATION BEING DRIVEN IN INCORRECT SEQUENCE

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• In WebSphere Application Server V6.1, the following exception
  may occur when an application uses the Extended JTA interface:
  .
  java.lang.IllegalStateException: Preparing
          at
  com.ibm.ejs.container.ContainerTx.ensureActive(ContainerTx.java:
  443)
          at
  com.ibm.ejs.container.ContainerTx.preInvoke(ContainerTx.java:151
  7)
          at
  com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContaine
  r.java:3402)
          at
  com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2
  856)
          at
  com.ibm.itim.transaction.EJSLocalStatelesswf_ejb_enroleejb_Trans
  actionComp_124a3c2d.beforeCompletion(Unknown Source)
          at
  com.ibm.itim.transaction.was.TransactionCompletionAdapter.before
  Completion(TransactionCompletionAdapter.java:52)
  
          at
  com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCo
  mpletion(SynchronizationCallbackWrapper.java:65)
  ...
  This occurs because ExtendedJTATransaction synchonizations are
  driven in an incorrect sequence.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IBM WebSphere Application Servers        *
  *                 version 6.1 users of ExtendedJTATransaction  *
  ****************************************************************
  * PROBLEM DESCRIPTION: IllegalStateException: Preparing        *
  *                      occurred when using the                 *
  *                      ExtendedJTATransaction interface        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  java.lang.IllegalStateException: Preparing
  at
  com.ibm.ejs.container.ContainerTx.ensureActive(ContainerTx.java:
  443)
  at
  com.ibm.ejs.container.ContainerTx.preInvoke(ContainerTx.java:151
  7)
  at
  com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContaine
  r.java:3402)
  at
  com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2
  856)
  at
  com.ibm.itim.transaction.EJSLocalStatelesswf_ejb_enroleejb_Trans
  actionComp_124a3c2d.beforeCompetion(Unknown Source)
  at
  com.ibm.itim.transaction.was.TransactionCompletionAdapter.before
  Completion(TransactionCompletiondapter.java:52)
  at
  com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCo
  mpletion(SynchronizationCallbacWrapper.java:65)
  ...
  This occurs because ExtendedJTATransaction Synchronizations
  are driven in an incorrect sequence.
  The root cause of this error is that Synchronizations
  registered (by calling the
  registerSynchronizationCallbackForCurrentTran(Synchronization)
  method) are registered with the transaction, but in the wrong
  tier of Synchronization objects, resulting in them being
  called after the EJBContainer Synchronization.
  

Problem conclusion

• Class ExtendedJTATransactionImpl will be changed to ensure
  that when Synchronization objects are registered with the
  transaction service by calling the
  registerSynchronizationCallbackForCurrentTran(Synchronization)
  method, they are in turn registered with the transaction in
  the correct tier of Synchronzations.
  In addition class RegisteredSyncs will be changed to ensure
  that Synchronization objects registered via the
  registerSynchronizationCallback(Synchronization) will be
  called last during the afterCompletion process.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.1.0.9. Please refer to the recommended updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• 6.1.0.7-WS-WAS-IFPK41846.pak
  

Comments

APAR Information

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

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

Modules/Macros

• TRAN
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSN

     UP

• R60H PSN

     UP

• R60I PSN

     UP

• R60P PSN

     UP

• R60S PSN

     UP

• R60W PSN

     UP

• R60Z PSN

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP