PM70437: TRANSACTION MANAGER NOT RESTARTING CORRECTLY WHEN FEATURE CONFIG URATION IS CHANGED.

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• If a Liberty profile server includes the jdbc and servlet
  features, and the servlet feature is removed and re-added, the
  transaction manager component may not restart correctly and
  may issue the following messages:
  
  [ERROR   ] [TMService] Error during instantiation of the
  implementation object Bundle:com.ibm.tx.jta(id=62)
  java.lang.IllegalArgumentException: Hook previously registered
  [ERROR   ] [TMService] Failed creating the component instance;
  see log for reason Bundle:com.ibm.tx.jta(id=62)
  [ERROR   ] [TransactionManager] Cannot create component
  instance due to failure to bind reference tmService
  Bundle:com.ibm.ws.transaction(id=61)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile using the JDBC and   *
  *                  servlet features.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: The transaction manager cannot be       *
  *                      activated more than once in a single    *
  *                      run of a server.  Trying to activate    *
  *                      it for a second time results in error   *
  *                      messages and the service is not         *
  *                      usable.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The transaction manager cannot be activated more than once in
  a single run of a server.  Trying to activate it for a second
  time results in error messages and the service is not usable.
  It is seen in the following scenario:
  If a server includes the jdbc and servlet features, and the
  servlet feature is removed and re-added, the transaction
  manager component may not restart correctly and may issue the
  following messages:
  [ERROR   ] [TMService] Error during instantiation of the
  implementation object Bundle:com.ibm.tx.jta(id=62)
  java.lang.IllegalArgumentException: Hook previously registered
  [ERROR   ] [TMService] Failed creating the component instance;
  see log for reason Bundle:com.ibm.tx.jta(id=62)
  [ERROR   ] [TransactionManager] Cannot create component
  instance due to failure to bind reference tmService
  Bundle:com.ibm.ws.transaction(id=61)
  

Problem conclusion

• The TMService registers a shutdown handler every time its
  constructed. The second time the TMService is initialized, its
  attempting to re-add the shutdown handler.  The unnecessary
  registration of the shutdown call has been removed.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.0.1. 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP