PQ95763: WLM CODE NEEDS TO CATCH EXCEPTION WHEN THE TRANSACTION MANAGER IS NOT READY.

APAR status
Closed as program error.

Error description
Environment:
Websphere 5.0.2.4 ND Cluster env on AIX, version 5.2
Abstract   :
WLM code needs to catch exception when the transaction manager
is not ready.

When the AppServer try to bind the resources to the name server
during the Server startup WLM code is trying to use the Transact
ion Manager though it is not ready and getting the exception
but WLM code is not catching the exception
Stack from the SystemOut
[10/7/04 22:55:58:579 MST] 504d7e4f ResourceMgrIm E WSVR0017E:
Error
encountered binding the J2EE resource, matrix_datasource, as
jdbc/matrix_datasource from
file:/usr/WebSphere/AppServer/config/cells/prod/resources.xml
com.ibm.ejs.jts.jts.CurrentSet$InitializationError: not
initialized
 at com.ibm.ejs.jts.jts.CurrentSet.self(CurrentSet.java:264)
 at
com.ibm.ejs.jts.jts.CurrentSet.get_control(CurrentSet.java:330)
 at
com.ibm.ws.wlm.client.affinity.TransactionAffinityModule.testAnd
SetAffin
ity(TransactionAffinityModule.java:189)
 at
com.ibm.ws.wlm.client.affinity.AffinityManager.getAffinityId(Aff
inityMan
ager.java:327)
 at
com.ibm.ws.wlm.client.affinity.AffinityManager.getTargetUsingAff
inity(Af
finityManager.java:189)
 at
com.ibm.ws.wlm.client.WLMClientLegacyImpl.getNextTarget(WLMClien
tLegacyI
mpl.java:211)
 at
com.ibm.ws.wlm.client.WLMClient.getNextTarget(WLMClient.java:177
)
 at
com.ibm.rmi.corba.ClientDelegate._createRequest_WLM(ClientDelega
te.java:
2011)
...
Local fix
removenode from the cell and addnode again.
Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users of        *
*                 Workload Management (WLM).                   *
****************************************************************
* PROBLEM DESCRIPTION: WLM code needs to catch exceptions      *
*                      when the transaction manager is not     *
*                      ready                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the Application Server tries to bind the resources to the
name server during the Server startup WLM code is trying to use
the Transaction Manager though it is not ready. WLM code is
getting the exception but is not catching the exception
Problem conclusion
Put code in place that doesn't allow offending exception out.

This APAR is built and included in the 5.0.2.9 fixpak.

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 PQ95763
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-10-14
Closed date 2004-12-03
Last modified date 2004-12-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WLM          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ95763
IBM Group: Software Group
Modified date: Dec 3, 2004