PQ65941: NAMING CODE CALLS ADMINSERVER WITHIN CONTEXT OF TRANSACTION AND CAUSES AN UNDESIRED TWO-PHASE TRANSACTION


APAR

APAR status
Closed as program error.

Error description
The problem is caused by the naming code calling the AdminServe
within the context of the Transaction. This forces the JTS to
propagate the Tx to the AdminServer. This action is unwanted an
causes the error: illegal use of 1 phrase results in transaction
and 2 phrase attempted with 1 phase results.
It seems the Inter-Server request made to
org.omg.ExtendedNaming._NamingContextStub.resolve() needs to be
handled outside of the transaction context.
Local fix
intermittent problem - no known workaround
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Release 3.5.6 or any releases prior          *
*                 to 3.5.6.                                    *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: With the current naming                 *
*                      implementation, a JNDI call to          *
*                      AdminServer is done within the          *
*                      context of a current                    *
*                      transaction unintentionally.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The naming remote naming server calls was forced to be part of
the user transaction with the current naming implementation,
which could result in the following failure scenarios:

1> A user defines a 1PC resource. After the transaction
begins, user may get the following warning message on the
console: "warning: Illegal use of 1 phase resource in
transaction, 2 phase commit was attempted with 1 phase
resource" if a JNDI call to Admin Server was made within the
current transaction.  The reason for this is: the involvement
of AdminServer, which is treated as the second server, is
forced the current transaction to be 2 phase commit
transaction.

2> After a TRANSACTION_ROLLEDBACK exception was thrown, a JNDI
call to AdminServererver will cause another
TRANSACTION_ROLLEDBACK exception since the JNDI call was
unintentionally performed in a rolled back transaction.

The fix for both WebSphere Application Server Release 3.5 and
4.0 was integrated in CMVC with PQ65485.
which could result in the following failure scenarios:1>, A user defines a 1PC resource. After the transactionbegins, user may get the following warning message on theconsole: "warning: Illegal use of 1 phase resource intransaction, 2 phase commit was attempted with 1 phaseresource" if a JNDI call to Admin Server was made within thecurrent transaction. The reason for this is: the involvementof AdminServer, which is treated as the second server, isforced the current transaction to be 2 phase committransaction.2>, After a TRANSACTION_ROLLEDBACK exception was thrown, a JNDIcall to AdminServererver will cause anotherTRANSACTION_ROLLEDBACK exception since the JNDI call wasunintentionally performed in a rolled back transaction.The fix for both WebSphere Application Server Release 3.5 and, 4.0 was integrated in CMVC withPQ65485.
Problem conclusion
The fix for this problem is to suspend the current transaction
before a JNDI makes a call to adminServer and resume the
tranascation after the call is finished.
Temporary fix
Shipped PQ65941_ujc.jar along with readme.txt to
wasdoc0\apars\PQ65941\3.5.6.
Comments
APAR information
APAR numberPQ65941
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-09-05
Closed date2002-12-04
Last modified date2002-12-04

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
NAMING
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ65941
IBM Group: Software Group
Modified date: 2002-12-04