• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NameNotFoundException when running WebSphere Cluster

 
Jan Tvorup
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I've been given the task of setting up an application for clustering using WebSphere 6.0 Network Deployment. I've managed to set up the cluster (a cell having a deployment manager and two nodes with an application server in each), and it works fine using the BeenThere application that came with the WebSphere installation.

The next step is getting the application up and running on WebSphere, and since I'm not much of a J2EE-programmer (yet!), this has proven difficult.

The application consists of two EJBs and a client that connects using IIOP. When deploying directly to an application server it works fine, but when deploying to the cluster, I get the following exception:

Exception in thread "P=248405 =0:CT" java.lang.RuntimeException: javax.naming.NameNotFoundException: Context: KPMCell/nodes/KPMDmgr/servers/dmgr, name: ejb/ClusterAppService: First component in name ClusterAppService not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0]
at test.kp.clusterapp.spec.service.ClusterAppServiceDelegate$ClusterAppServiceJNDIProxy.<init>(ClusterAppServiceDelegate.java:1494)
at test.kp.clusterapp.spec.service.ClusterAppServiceDelegate.<init>(ClusterAppServiceDelegate.java:87)
at test.kp.clusterapp.client.OpgClientCluster.<init>(OpgClientCluster.java:16)
at test.kp.clusterapp.client.OpgClientCluster.main(OpgClientCluster.java:40)
Caused by: javax.naming.NameNotFoundException: Context: KPMCell/nodes/KPMDmgr/servers/dmgr, name: ejb/ClusterAppService: First component in name ClusterAppService not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException(CNContextImpl.java:4394)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1784)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at test.kp.clusterapp.spec.service.ClusterAppServiceDelegate$ClusterAppServiceJNDIProxy.<init>(ClusterAppServiceDelegate.java:1486)
... 3 more

I guess this is some sort of JNDI-problem, where either the EJB's are not registerred in the server or the client makes the lookup in the wrong place.

I am running the client on my own computer using the VM that came with my installation of WebSphere (v6.0, but not Network Deployment).

Thanks in advance,
Jan Tvorup
 
Niranjan Sarkar
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Try by appending the cluster name preceding to the existing JNDI location.
Do keep me posted on your results!
Regards,
Niranjan
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic