IBM Support

PI49306: ZWAS: BATCH JOB USING WOLA SERVICE HUNG AFTER SERVER RECYCLE DUE TO WAIT IN BBOCLSCC IN LOCAL COMM CONNECT()

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A Cobol batch job using WOLA service hung indefinitely. A dump
    of the job shows that there is a thread hung waiting for a
    response from a zWAS server that has already been recycled.
    The thread native and linkage stacks show the flow of control
    between the following modules leading up to the wait in BBOCLSCC
    for Comm Local Connect() processing.
    BBOAINV -> BBOAAPI -> BBOATRUP -> BBODPCN8 -> bbodpcrt ->
    BBOCLSCC.
    The root cause is a narrow window between server shutdown and
    application startup.
    This APAR was taken to improve product reliability by augmenting
    the WOLA client to take advantage of the local comm timeout
    introduced by PM61861.
    With this code change the WOLA batch job thread will timeout
    allowing the job to terminate gracefully.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere Application Server       *
    *                  using Optimized local Adapters for          *
    *                  WebSphere V8.0 and V8.5                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Optimized Local Adapter       *
    *                      (WOLA) cllents hang when connecting to  *
    *                      a Websphere server that is being        *
    *                      shut down.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The existing wait time defined on the WOLA API's BBOA1CNG,
    BBOA1RCA, BBOA1INV and BBOA1SRV was not being honored when
    creating a connection to the server. In addtion the WOLA
    API BBOA1REG does not have a connection timeout defined when
    establishing new connections for the connection pool
    

Problem conclusion

  • The wait time parameter defined on the WOLA API's BBOA1CNG,
    BBOA1RCA, BBOA1INV and BBOA1SRV is now honored when
    connecting to the server. In addition, a default wait time
    of 60 seconds is used by the BBOA1REG API when establishing
    new connections for the connection pool.
    
    APAR PI49306 is currently targeted for inclusion in Fix Packs
    8.0.0.13 and 8.5.5.10 of WebSphere Application Server.
    
    In addition, sysroute APAR PI61046 will provide the fix in
    WebSphere Application Server V7.0 Fix Pack 7.0.0.43.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49306

  • 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

    2015-09-24

  • Closed date

    2016-04-19

  • Last modified date

    2017-03-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI61046

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 850

Reference #: PI49306

Modified date: 28 March 2017