IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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 number

    PH03840

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-09

  • Closed date

    2019-03-28

  • Last modified date

    2019-03-28

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCWL8S","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 March 2019