PH03840: ATTEMPTING TO CREATE A NEW ILCONTAINER AFTER SQLEXCEPTION CAUSES COM.IBM.WEBSPHERE.BATCH.ILC.ILCONTAINEREXCEPTION

9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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

• The existing code doesn't allow for an ILContainer to be
  recreated in the case of a SQLException.  A call to get a new
  ILContainer just returns the previous one (which is no good).
  This APAR will be used to change an existing protected method
  clearContainerFromThread to public so that application code can
  create a new ILContainer instead.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  Java Batch Cobol container                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Can no longer use the ILContainer to    *
  *                      call COBOL modules after a              *
  *                      SQLException has occurred because of a  *
  *                      deadlock or timeout on the DB2 side.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the Java Batch Cobol container ILContainer with
  DB2, a deadlock or timeout while using DB2 can leave the
  underlying PIPI environment in an unusable state.  It is not
  enough for the application to handle the thrown exception and
  to obtain a new ILContainer object, as the existing one
  will be used again.  The ILContainer object must be cleared
  using the clearContainerFromThread() method, which was a
  protected method.
  

Problem conclusion

• The ILContainerFactory.clearContainerFromThread() API method
  has been changed from protected to public.  This will allow an
  application to use it without need for reflection.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.11 and 8.5.5.16.  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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R900 PSY

     UP