PQ78401: When running Java app using RMI/IIOP in WSAS 4.0.6 and higher generic server, JTS "not initialized" occurs | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In WebSphere Application Server (WSAS) 4.0.5 and above, a Java application running in the generic server (as opposed to a managed server) using RMI/IIOP generated the following exception in the stderr when the generic server is started: Exception in thread "P=94562:O=0:CT" javax.naming.NamingException: MQWFAGENT. Root exception is com.ibm.ejs.jts.jts.CurrentSet$InitializationError: not initialized at com.ibm.ejs.jts.jts.CurrentSet.self(CurrentSet.java:218) at com.ibm.ejs.jts.jts.CurrentSet.get_control(CurrentSet.java:265) at com.ibm.ejs.jts.jts.Current.get_control(Current.java:72) at com.ibm.ws.naming.util.Helpers.suspendTransaction(Helpers.java:1 412) at com.ibm.ejs.ns.jndi.CNContextImpl.cosRebindCorbaObject(CNContext Impl.java:2925) at com.ibm.ejs.ns.jndi.CNContextImpl.doRebind(CNContextImpl.java:18 37) at com.ibm.ejs.ns.jndi.CNContextImpl.rebind(CNContextImpl.java:609) at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:168) at javax.naming.InitialContext.rebind(InitialContext.java:375) at com.ibm.workflow.iiop.jni.DomainControllerImpl.<init>(DomainCont rollerImpl.java:249) at com.ibm.workflow.agent.Main.main(Main.java:78)Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * Naming JNDI, who has the release 4.0.7 * * or the release prior to 4.0.7 installed, * * or who has the release 5.0.2 or the release * * prior to 5.0.2 installed. * **************************************************************** * PROBLEM DESCRIPTION: In the case where JTS fails to be * * initialized in a non WebSphere * * application server - a generic server, * * a JNDI operation will fail with a * * NamingException, whose root exception * * is com.ibm.ejs.jts.jts. * * CurrentSet$InitializationEroor: * * not initialized. * **************************************************************** * RECOMMENDATION: * **************************************************************** Transaction is being suspended during a Naming operation that requires name server accesses. In the case where JTS fails to be initialized in a non WebSphere application server - a generic server, a Naming operation will fail with a NamingException, whose root exception is: com.ibm.ejs.jts.jts.CurrentSet$InitializationEroor: not initialized.Problem conclusion Implemented a try block to catch any exception thrown while getting hold of a transaction so that the Naming operation can be continued.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ78401
IBM Group: Software Group
Modified date: Oct 15, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.