IBM Support

PI27448: THREAD HANG RECOVERY NOT TERMINATING A THREAD IN DB2 TYPE 2 DRIVER ENV WITH WEBSPHERE FOR Z/OS.

Fixes are available

8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Thread Hang Recovery not terminating a thread in DB2 type 2
    driver env with WebSphere for z/OS.
    
      If the DB2 Type 2 ODI can not register, an application request
     may drive into DB2 and be stuck.   The Thread Hang Recovery
     code is invoked when a timeout of the application occurs. It
     will invoke the ODI's that are currently registered for the
     associated Hung request.
      If the application request can not be encouraged to complete
     then the Server may be ABTERM'd with ABEND CODE EC3 and a
     timeout reason code (ex. 04130004).
    
      This customer received an ABEND EC3, RSN=04130004 while a
     dispatched request was running in DB2.   If the DB2 Type 2 JDBC
     Driver had registered its ODI then the ABEND may have been
     prevented; the DB2 ODI could have interrupted the DB2 request
     and allowed the application request to complete.
    
      The issue is that the ODI may not always be
     registered from the DB2 type 2 driver. There is an issue that
    the DB2 driver needs to be able to see the ODI registration
    interace (interrupt/iti) only at
     the time it is started. In some cases it appears that the
    binding of the ODI
     registration interface to naming does not happen early enough
    and DB2 does not see the registration interface during the DB2
    type 2 driver's initialization.   Hence the thread cannot be
    terminated by DB2's ODI when the
     InterruptibleThreadInfrastructure triggers. So in this case the
     EC3 is then used to terminate the servant region if configured
     for termination.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application server for z/OS   *
    *                      may ABEND a Servant request running     *
    *                      under a DB2 Type 2 driver after a       *
    *                      timeout.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The DB2 Type 2 driver has implemented an ODI (InterruptObject)
    that, when called, can interrupt the associated request.  There
    is a timing problem, during Servant initialization, that the
    reference to the InterruptibleThreadInfrastructure needed to
    register/deregister an ODI isn't available to the
    DB2 Type 2 driver initialization code.   This prevents the
    DB2 Type 2 driver from registering its ODI to enable the
    Thread Hang Recovery code to interrupt the dispatched request
    for timeout scenarios.
    If the request can't be interrupted, then the controller may
    issue an ABENDEC3 to terminate the Servant for the request
    timeout.  The following is a list of likely request timeout
    abend reason codes for the ABENDSEC3 received for this
    problem: 04130004, 04130007 and 04130008.
    

Problem conclusion

  • Code has been modified within the Server initializatioin code
    to ensure that the interrupt/iti naming reference is available
    before the Servant initialization code which drives the DB2
    Type 2 driver initialization.
    
    APAR PI27448 is currently targeted for inclusion in Fix Packs
    8.0.0.10 and 8.5.5.5 of WebSphere Application Server.
    
    Sysroute APAR PI28509 will be used to delivered the fix in
    WebSphere Application Server V7.0.
    
    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

    PI27448

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-10-10

  • Closed date

    2014-10-27

  • Last modified date

    2014-10-27

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

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

    PI28509

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 #: PI27448

Modified date: 27 October 2014