PQ69389: GENERIC XASESSION.CLOSE() CLOSES NONXASESSION

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
When an application using XASessions, closes its
session, the runtime closes the nonASFSession. For some Generic
JMS providers this causes them to also close the XASession. This
is illegal as the session is enlisted in an active global
transaction. The JMS specification does not indicate to JMS
provider implementors how they should implement session.close()
for an XA encapsulated session. Thus the runtime should delay
closing both the XASession and its encapsulated nonXASession
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users using Generic "other" JMS providers    *
*                 that are XA capable and have                 *
*                 XASession.close() symantics that close       *
*                 the XASession when the wrapped session       *
*                 is closed, rather than at end of             *
*                 transaction.                                 *
****************************************************************
* PROBLEM DESCRIPTION: XASession wrapped session closed too    *
*                      early for Generic JMS providers.        *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Some Generic "other" JMS providers have XASession.close()
symantics that close the XASession when the wrapped session
is closed, rather than at end of the transaction. This means
when the runtime tries to close the wrapped session, it closes
the XASession and hence causes transaction problems.
Problem conclusion
Generic JMS provider XA session wrapped sessions are
deferred to be closed at end of transaction.
Temporary fix
Sent eFix to customer for testing.
Comments
APAR information
APAR number PQ69389
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-12-23
Closed date 2003-01-24
Last modified date 2003-01-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69389
IBM Group: Software Group
Modified date: Jan 24, 2003