PM46173: SETTING TX TIMEOUT USING THE UOWMANAGER INTERFACE TO NOT WORKING, RESULTING IN UNEXPECTED WTRN0006W AND TX ROLLBACK

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When one uses the UOWManager interface to set the tx timeout by
  using the following annotation
  
  @Transactional(timeout=...) annotation
  
  the tx timeout specified is not being handled properly by
  WebSphere Application Server.  The result is that the tx timeout
  is not changed and so the tx times out using the default tx
  timeout.
  .
  The result is the following messages.
  [8/18/11 15:02:55:997 EDT] 00000000 TimeoutManage I   WTRN0006W:
  
  Transaction
  XXXXXXXXX has timed out after 120 seconds.
  .
  and
  .
  [8/18/11 15:04:03:450 EDT] 00000000 LocalTransact E   J2CA0026E:
  Method addSync caught javax.transaction.RollbackException:
  Transaction rolled back
  at
  com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronizati
  on(TransactionImpl.java:3589)
  at
  com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronizati
  on(TransactionImpl.java:3568)
  

Local fix

• change the tx timeout using the configuration parameters, but
  this will affect other txs, or use the container tx settings.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Attempting to alter the transaction     *
  *                      timeout through the UOWManager          *
  *                      interface does not change the setting.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The transaction timeout setting for new units of work started
  by the UOWManager continues to use the server transaction
  timeout default rather than the setting configured on the
  UOWManager.
  

Problem conclusion

• Change to ensure that the transaction is started with the
  appropriate timeout value.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.43.  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP