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

Obtain the fix for this APAR.

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 V7.0                                  *
  ****************************************************************
  * 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 PI28509 is currently targeted for inclusion in Fix Pack
  7.0.0.37 of WebSphere Application Server.
  
  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 is sysrouted FROM one or more of the following:

  PI27448

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

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UI25330

     UP15/03/13 P F503

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.