WebSphere for z/OS Java(TM) Client ejbivp.bat fails with javax.naming.ServiceUnavailableException
 Technote (FAQ)
 
Problem
The customer tried to run the WebSphere z/OS Java Client by running the EJBIVP.BAT file downloaded on a Windows 2000 PC. The client failed with the following errors:

*********** bmp bean will be run!
Look up policy session home
Obtaining policysession bean jndi name...
The policysession bean jndi name is:
/ILPOCOW/BBOASR2/PolicyIVP/Policy/PolicySession/com.ibm.ws390.samples.ivp.ejb.
PolicySessionHome
IVP has failed
javax.naming.ServiceUnavailableException: Caught exception when
resolving initial reference=NameService. Root exception is org.omg.CORBA.INV_OBJREF:
minor code: 1398079490 completed: No
at com.sun.corba.se.internal.core.CodeSetComponentInfo.read(Unknown Source)
at com.sun.corba.se.internal.core.Profile.<init>(Unknown Source)
at com.sun.corba.se.internal.core.IOR.getProfile(Unknown Source)
at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(Unknown Source)
at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(Unknown Source)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(Unknown Source)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(Unknown Source)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(Unknown Source)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(Unknown Source)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:362)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCt
xFactory.java:315)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtx
Factory.java:172)
at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(W
snInitialContextFactory.java:89)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.ibm.ws390.samples.ivp.client.TestClient.main(TestClient.java:89)
 
Cause
The output from the java -version command for the customer displayed the following:

java version "1.3.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02) Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode)

 
Solution
One suggested workaround to enable the EJBIVP.BAT to run is to edit the absolute path of EJBIVP.BAT to contain the absolute path that points to IBM's version of the JRE. There are two lines that need to be edited. You should determine where the IBM JRE resides on the workstation. The default locations are:

C:\jdk1.1.8\
C:\WSDK\sdk

In the EJBIVP.BAT file the two lines that look like the following:

java -Djava.naming.provider.url=%PROVIDER_URL% -DSESSION_NAME......

The word JAVA in both places should be changed and replaced with the absolute path which would look like:


/WSDK/SDK/bin/java -Djava....
or
/jdk1.1.8/bin/java -Djava...

In this case the IBM JRE will be picked up only for this particular batch file. If the intent is to make the change permanent then the for the workstation should point to the absolute path for IBM's JRE. IBM's JRE is required on Windows because the IBM client jar is needed for the JNDI over LDAP communication. This communication is made by hooking into the IBM ORB and the IBM JVM is required to accomplish this.

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1163962
IBM Group: Software Group
Modified date: Mar 23, 2004