Java Naming and Directory Interface™ (JNDI) Lookup Fail From a Stand-alone Enterprise Bean
 Technote (FAQ)
 
Problem
Performing a JNDI lookup from a stand-alone enterprise bean throws a CurrentSet$InitializationError exception. This is applicable to V4.0.5 through V5.0.2.1 releases.
 
Cause
Beginning with the WebSphere® Application Server V4.0.5 release, performing a JNDI lookup from an enterprise bean running in a stand-alone Java™ virtual machine (JVM™) results in the following exception:

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:1412)
at com.ibm.ejs.ns.jndi.CNContextImpl.cosRebindCorbaObject(CNContextImpl.java:2925)
at com.ibm.ejs.ns.jndi.CNContextImpl.doRebind(CNContextImpl.java:1837)
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>(DomainControllerImpl.java:249)
at com.ibm.workflow.agent.Main.main(Main.java:78)

This problem is fixed by APAR PQ78401
 
Solution
Apply APAR PQ78401.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server Enterprise Security AIX, HP-UX, Linux, Solaris, Windows 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2 Edition Independent
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1175740
IBM Group: Software Group
Modified date: Aug 1, 2004