PI51364: TRANSACTION CONTEXT LEFT ON WEBCONTAINER THREAD WHEN INTERNAL ERROR OCCURS MAKING AN OUTBOUND WEB SERVICE REQUEST.

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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

• An NullPointerException within the web services component can
  result in failure to reactivate an inactive transaction
  association with the thread during processing of an outbound
  web service request. When this occurs in the Web Container,
  the container tries but fails to rollback the transaction and
  the inactive transaction remains associated with the thread.
  
  An example partial call stack for the initial error is shown
  below:
  
  Caused by: java.lang.NullPointerException
   at
  org.apache.axis2.util.ThreadContextMigratorUtil.performContextCl
  eanup(ThreadContextMigratorUtil.java:185)
   at
  org.apache.axis2.jaxws.core.controller.impl.AxisInvocationContro
  ller.postExecute(AxisInvocationController.java:654)
   at
  org.apache.axis2.jaxws.core.controller.impl.AxisInvocationContro
  ller.execute(AxisInvocationController.java:586)
   at
  org.apache.axis2.jaxws.core.controller.impl.AxisInvocationContro
  ller.doInvoke(AxisInvocationController.java:127)
   at
  org.apache.axis2.jaxws.core.controller.impl.InvocationController
  Impl.invoke(InvocationControllerImpl.java:93)
   at
  org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIM
  ethod(JAXWSProxyHandler.java:419)
   at
  org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAX
  WSProxyHandler.java:213)
   at com.sun.proxy.$Proxy102.executeTokenTransNoEncrypt(Unknown
  Source)
  
  When the thread is dispatched on subsequent requests,
  attempts to begin a new transaction will fail and the message
  "WTRN0017W:Unable to begin a nested transaction. Nested
  transactions are not supported." will be generated in SystemOut.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of Web   *
  *                  Services Atomic Transactions (WS-AT).       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Beginning a JTA transaction on a Web    *
  *                      Container thread unexpectedly fails     *
  *                      with                                    *
  *                      javax.transaction.NotSupportedException *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An error in the web services component caused that component
  to fail to invoke the transaction service's
  ThreadContextMigrator on the response path of a Web service
  request.  Subsequent attempts to rollback the transaction,
  including by the Web container, fail since the internal state
  of the transaction indicates that the current thread is not
  entitled to perform the rollback.  In such a case the
  transaction remains associated with the thread.  When the Web
  Container thread is reused on subsequent requests the
  transaction context is still associated with the thread though
  its state renders it unusable.
  

Problem conclusion

• The code was modified so that a transaction in this state would
  be marked for rollback only and disassociated from the thread
  when the Web Container tried to rollback the transaction.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  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