|
Problem |
When running BBOIVPE job, the following
error messages may be issued:
javax.naming.NameNotFoundException: ?LDAP: error code 32 - No Such
Object?; remaining name 'ibm-wsnName=com.ibm.ws390.samples.ivp.e
jb.PolicySessionHome,ibm-wsnName=ivp.policysession,ibm-wsnName=policyses
sion_deploy,ibm-wsnName=PolicyIVP,ibm-wsnName=CB390,ibm-wsn
Name=WebSphere390,ibm-wsnName=appl'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2775)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2696)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2502)
at com.sun.jndi.ldap.LdapCtx.c_getAttributes(LdapCtx.java:1157)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDir
Context.java:228)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Partial
CompositeDirContext.java:137)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Partial
CompositeDirContext.java:125)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Partial
CompositeDirContext.java:115)
at
com.ibm.ws.naming.ldap.WsnLdapContextImpl.lookup(WsnLdapContextImpl.java
:938)
at
com.ibm.ws.naming.ldap.WsnLdapContextImpl.lookup(WsnLdapContextImpl.java
:1048)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ws390.samples.ivp.client.TestClient.main(TestClient.java:96)
From the ejbivp.sh:
.
java
-DSESSION_NAME=/session/com.ibm.ws390.samples.ivp.ejb.PolicySessionHomecom.ibm.ws390.samples.ivp.client.TestClient
bmp
From the dump of the name space:
ibm-wsnName=com.ibm.ws390.samples.ivp.ejb.PolicySessionHome,ibm-wsnName=PolicySession,ibm-wsnName=Policy,ibm-wsnName=PolicyIVP,ibm-wsnName=BBOASR4A,ibm-wsnName=PLEX1,ibm-wsnName=legacyRoot,ibm-wsnName=PLEX1,ibm-wsnName=domainRoots,ibm-wsnTree=t1,o=WASNaming,c=us
Note: The above entries show 2 different paths for the same HOME
|
|
|
|
Solution |
Use LDAP browser or the following commands to look at the
namespace:
export LDAP_BASEDN="o=WASNaming,c=US"
ldapsearch -v -p 1389 "objectclass=*" > name.space
(if you did not use defaults, substitute "o=WASNaming,c=US" for the root
you chose)
The problem is the ejbivp.sh file is from an older version of
WebSphere® Application Server V 4.0. SESSION_NAME in WebSphere®
Application Server V4.0.1 was changed.
Look in your DATA (created after customization panels were run) at the
member BBOWIVP2, you will see a script that should have been copied into
the HFS. You can either copy it to HFS and run BBOIVPE again, or
substitute the SESSION_NAME with the path showed by namespace output. It
would like the following but on one line:
java
-DSESSION_NAME=/PLEX1/BBOASR2/PolicyIVP/Policy/PolicySession/com.ibm.ws390.samples.ivp.ejb.PolicySessionHome
com.ibm.ws390.samples.ivp.client.TestClient bmp
|
|
|
|
|
|
|