PQ72384: _PREINVOKE NOT CALLED WHEN GETMETADATA CALLED ON CONNECTION, THUS CONNECTION NOT ENLISTED IN CURRENT TRANSACTION

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
WebSphere Application Server Connection Manager Cumulative Fix
4.0.2-4.0.7: Component cumulative Connection Manager fix



APAR status
Closed as program error.

Error description
When getMetaData is called on a connection, the connection manag
er does not call preInvoke.  This means that the connection is n
ot enlisted in any running transactions.  Because of this, any s
ubsequent connections create their own local transactions.  The
original XA resource from the getMetaData call has not been comm
itted, so the database will return an XA error when the XA.start
 is called for the second transaction.
Local fix
The workaround is to hard code the select that is done under the
 covers when getMetaData is called.  This may be difficult for c
ustomers to implement.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of    *
*                 database connections.                        *
****************************************************************
* PROBLEM DESCRIPTION: When using getMetaData() on the         *
*                      connection, the user could get          *
*                      an XAerror on the next                  *
*                      transaction start.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When getMetaData is called on a connection, the connection
manager did not call preInvoke.  This means that the
connection is not enlisted in any running transactions.
Because of this, any subsequent connections create their own
local transactions.  The original XA resource from the
getMetaData call has not been committed, so the database will
return an XA error when the XA.start is called for the
second transaction.
Problem conclusion
Changed the code so we enlist (call preInvoke()) on
getMetaData() calls.
Temporary fix Comments
APAR information
APAR number PQ72384
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-03-24
Closed date 2003-04-30
Last modified date 2003-05-21

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
JDBC          

SRLS

Fix information

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 #: PQ72384
IBM Group: Software Group
Modified date: May 21, 2003