PK16432: J3CA0056I ERROR WHEN CLOSING A JMS CONNECTION FROM A SERVLET RUNNING INSIDE OF WEBSPHERE APPLIATION SERVER V5.X OR 6.X

 Fixes are available

6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for AIX platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for HP-UX platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for OS/400 platform
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Solaris
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Windows platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for AIX platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for HP-UX platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for HP-UX platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for AIX platforms
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for AIX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for HP-UX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Linux platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Solaris
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Windows platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Linux platforms
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
6.0.2.9: WebSphere Application Server V6.0.2 Fix Pack 9 for Windows platforms
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
6.0.2.11: WebSphere Application Server V6.0.2 Fix Pack 11 for Solaris platforms
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
6.0.2.13: WebSphere Application Server V6.0.2 Fix Pack 13 for AIX platforms
6.0.2.13: WebSphere Application Server V6.0.2 Fix Pack 13 for HP-UX platforms
6.0.2.11: WebSphere Application Server V6.0.2 Fix Pack 11 for Windows platforms
6.0.2.11: WebSphere Application Server V6.0.2 Fix Pack 11 for HP-UX platforms
6.0.2.11: WebSphere Application Server V6.0.2 Fix Pack 11 for Linux platforms
6.0.2.13: WebSphere Application Server V6.0.2 Fix Pack 13 for Windows platforms
6.0.2.13: WebSphere Application Server V6.0.2 Fix Pack 13 for Linux platforms
6.0.2.15: WebSphere Application Server V6.0.2 Fix Pack 15 for OS/400
6.0.2.15: WebSphere Application Server V6.0.2 Fix Pack 15 for HP-UX
6.0.2.9: WebSphere Application Server V6.0.2 Fix Pack 9 for Solaris platforms
6.0.2.9: WebSphere Application Server V6.0.2 Fix Pack 9 for AIX platforms
6.0.2.9: WebSphere Application Server V6.0.2 Fix Pack 9 for HP-UX platforms
6.0.2.9: WebSphere Application Server V6.0.2 Fix Pack 9 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Solaris
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Windows platforms
6.0.2.15: WebSphere Application Server V6.0.2 Fix Pack 15 for AIX
6.0.2.15: WebSphere Application Server V6.0.2 Fix Pack 15 for Solaris
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for AIX platforms
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for OS/400 platform
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for Solaris
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for Windows platforms
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for HP-UX platforms
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for AIX platforms
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
6.0.2.11: WebSphere Application Server V6.0.2 Fix Pack 11 for AIX platforms
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for HP-UX platforms
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for Windows platforms
6.0.2.13: WebSphere Application Server V6.0.2 Fix Pack 13 for Solaris platform
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for OS/400 platform
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for HP-UX platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Linux platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Windows platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Solaris
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for OS/400 platform
6.0.2.15: WebSphere Application Server V6.0.2 Fix Pack 15 for Windows
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Linux platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for AIX platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Windows platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Solaris platforms
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for Solaris
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for Linux platforms
6.0.2.19: WebSphere Application Server V6.0.2 Fix Pack 19 for Linux platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for AIX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for HP-UX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for OS/400 platform
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Linux platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Solaris
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Windows platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server



APAR status
Closed as program error.

Error description
When using a Websphere managed connection (i.e. one that is
created from a factory defined in the application server's
namespace), a list is kept of all the temporary destinations
created on that connection.  When the managed connection is
closed, the application server attempts to delete all of these
temporary destinations as per section 4.4.3 of the Java Message
Service Specification Version 1.1.

However, it is entirely possible that the application using the
managed connection has already deleted the temporary
destination, using the TemporaryQueue.delete() or the
TemporaryTopic.delete() methodes.

In this situation, the applicaton server will attempt to delete
a temporary destination that no longer exists, resulting in the
J2CA0056I error mentioned above.  The managed connection will
also be marked as stale, and will not be returned to the
connection pool.

This can occur with servlets running inside of WAS v5.x or 6.x.
You will see the following error in the server's SystemOut.log
file :

J2CA0056I: The Connection Manager received a fatal connection
error from the Resource Adaptor for resource <Resource Name>.
The exception which was received is javax.jms.JMSException:
MQJMS3001: temporary queue already closed or deleted
Local fix
To resolve the problem, the logic that deletes temporary
destinations when the connection is being closed has been
changed.

If an excepton occurs deleting a destionation, the
application server now checks to see if the reason for the
exception is because the queue or topic has already been
deleted.  If it is trying to delete something that has already
been
deleted, the exception is ignored.  If a different error has
occured however, the connection will be marked as stale and the
J2CA0056I mesage output to the SystemOut.log files as before.
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use       *
*                 the Java Message Service (JMS)               *
*                 functionality provided with WebSphere        *
*                 Application Server Version 5 and             *
*                 Version 6.                                   *
****************************************************************
* PROBLEM DESCRIPTION: When a servlet running inside of        *
*                      WebSphere Application Server Version    *
*                      5 or 6 creates and deletes              *
*                      temporary destinations (either queues   *
*                      or topics), closing the underlying JMS  *
*                      connection after all of the temporary   *
*                      destinations have been deleted          *
*                      results in the following error          *
*                      appearing in the application server's   *
*                      SystemOut.log file:                     *
*                                                              *
*                                                              *
*                      J2CA0056I: The Connection Manager       *
*                      received a fatal connection error       *
*                      from the Resource Adaptor for           *
*                      resource <Resource Name>.  The          *
*                      exception which was received is         *
*                      javax.jms.JMSException:                 *
*                      MQJMS3001: temporary queue already      *
*                      closed or deleted                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using a WebSphere managed connection (i.e. one that is
created from a factory defined in the application server's
namespace), a list is kept of all the temporary destinations
created on that connection. When the managed connection is
closed, the application server attempts to delete all of
these temporary destinations as per section 4.4.3 of the
Java Message Service Specification Version 1.1.

However, it is entirely possible that the application using
the managed connection has already deleted the temporary
destination, using the TemporaryQueue.delete() or the
TemporaryTopic.delete() methods.

In this situation, the application server will attempt to
delete a temporary destination that no longer exists,
resulting in the J2CA0056I error. The managed connection
will also be marked as stale, and will not be returned to
the connection pool.
Problem conclusion
The logic that deletes temporary destinations when the
connection is being closed has been changed. If an exception
occurs deleting a destination, the application server now
checks to see if the reason for the exception is because the
queue or topic has already been deleted. If it is trying to
delete something that has already been deleted, the exception
is ignored. If a different error has occurred, however, the
connection will be maked as stale and the J2CA0056I message
output to the SystemOut.log file as before.

The fix for this APAR is currently targeted for inclusion in
Cumulative Fix 16 for WebSphere Application Server Version
5.0.2, Cumulative Fix 9 for WebSphere Application Server
Version 5.1.1 and Fix Pack 9 for WebSphere Application Server
Version 6.0.2. Please refer to the Recommended Updates page
for delivery dates:

   
http://www-1.ibm.com/support/
     docview.wss?rs=180&context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PK16432
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-12-12
Closed date 2006-02-03
Last modified date 2006-04-03

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 BASE 5.0
Fixed component ID 5630A3600

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 #: PK16432
IBM Group: Software Group
Modified date: Apr 3, 2006