PK09325: DEADLOCK CONDITIONS AFTER SERVER SESSIONS ARE RETURNED TO POOL

 Fixes are available

PK09325; 5.1.1.4: Deadlock conditions after server sessions are returned to pool
PK09325; 5.1.1.4: Deadlock conditions after server sessions are returned to pool



APAR status
Closed as program error.

Error description
This APAR is to deliver an interim fix for 
PK02976, 
PK04470 et
al for all applicable releases of the product.  These packages
will be functionally identical to interim fixes already
available for 
PK02976 for most releases of the product, but for
5.1.1.2, this interim fix will add resolutions for additional
sources of deadlocks.
Local fix
Install the interim fix for 
PK02976 for all releases expect
5.1.1.2.  For 5.1.1.2, request test fix from change team.
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the   *
*                 Java Message Service (JMS) functionality     *
*                 provided with WebSphere Application Server   *
*                 Version 5.                                   *
****************************************************************
* PROBLEM DESCRIPTION: When using message-driven beans (MDBs)  *
*                      with WebSphere Application Server       *
*                      version 5, the MDBs stop                *
*                      processing messages either              *
*                      unexpectedly or following an error      *
*                      even though the Listener Port           *
*                      associated with the MDB is shown to     *
*                      be currently active. Attempts to stop   *
*                      the application server once the MDB     *
*                      has stopped processing messages         *
*                      results in a hang.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Over the past 6 months, a number of deadlock conditions in the
WebSphere Messaging code have been identified and been fixed.
These include the following APARs:

 
PQ99224 - DEADLOCK OCCURS DURING EXCEPTION HANDLING FOR MDB
 
PK00582 - ENLIST ERRORS CAUSE MESSAGE-DRIVEN BEANS TO STOP
           DETECTING MESSAGES
 
PK01477 - ENLIST ERRORS CAUSE MESSAGE-DRIVEN BEANS TO STOP
           DETECTING MESSAGES, AND THE APPLICATION SERVER TO
           HANG WHEN SHUTTING DOWN
 
PK02976 - JMS LISTENER PORT JAM AFTER QMGR RESTART
 
PK04470 - DEADLOCK CONDITION AFTER SERVER SESSION WAS RETURNED
           TO POOL AND MARKED AS EMPTY

The fixes for the APARs listed above are available as part of
Cumulative Fixes listed below:

 Cumulative Fix 11 for WebSphere Application Server
    Version 5.0.2 (or later)
 Cumulative Fix 5 for WebSphere Application Server
    Version 5.1.1 (or later)
 Cumulative Fix 2 for WebSphere Application Server
    Version 6.0.1 (or later)

However, not all customers are willing or able to apply the
latest Cumulative Fix for their version of the application
server.

This APAR has been raised to provide a single installable
fix that contains all of the APARs listed above for earlier
versions of WebSphere Application Server Version 5.x
Problem conclusion
A single installable fix that addresses all of the WebSphere
Messaging deadlock issues is now available for the following
releases:

  WebSphere Application Server Version 5.0.2.7
  WebSphere Application Server Version 5.0.2.8
  WebSphere Application Server Version 5.0.2.9
  WebSphere Application Server Version 5.0.2.10

  WebSphere Application Server Version 5.1.0.4

  WebSphere Application Server Version 5.1.1.0
  WebSphere Application Server Version 5.1.1.1
  WebSphere Application Server Version 5.1.1.2
  WebSphere Application Server Version 5.1.1.3
  WebSphere Application Server Version 5.1.1.4


The fix can be downloaded from the WebSphere Application
Server - Support web site:

  
http://www-306.ibm.com/software/webservers/
     appserv/was/support/
Temporary fix Comments
APAR information
APAR number PK09325
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-07-22
Closed date 2005-08-05
Last modified date 2005-08-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MSGING          

Publications Referenced

Fix information
Fixed component name WAS NETWRK DEPL
Fixed component ID 5630A3601

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK09325
IBM Group: Software Group
Modified date: Aug 5, 2005