IBM Support

PH13564: WOLA IS NOT FREEING IMS TPIPE AFTER AN ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using WebSphere Optimised Adapters (WOLA) to call
    transactions in IMS, after an error condition (ie timeout) the
    TPIPE is not freed resulting in eventually running out of free
    TPIPEs and requireing a server restart.
    Performing an IMS checkpoint 3 times does not help.
    

Local fix

  • Restart WAS Server
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V8.5                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      using WOLA to drive a transaction in    *
    *                      IMS, may leak a transaction pipe        *
    *                      (tpipe).                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WOLA implementation for the javax.resource.cci.Interaction
    interface, com.ibm.ws390.ola.jca.InteractionImpl, calls
    native from the execute method.   The native routines may
    use OTMA services: DFSYALOC, DFSYSNDX, ... to send request
    and return the response.  A path exists through the native
    routine sendRequestOTMA in bbgajni.cpp, that will invoke the
    OTMA DFSYALOC and DFSYSNDX, but not the DFSYFREE.  This will
    cause the allocated tpipe to become un-reusable and lead to a
    WebSphere server recycle to reclaim them.
    

Problem conclusion

  • Code has been added to the sendRequestOTMA to drive the OTMA
    DFSYFREE to release the tpipe prior to returning.  This call
    was missing on a couple of exception flows through the
    routine.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.17 and 9.0.5.2.  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

    PH13564

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-19

  • Closed date

    2019-08-09

  • Last modified date

    2019-08-09

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021