Problem getting JNDI context in WAS 5.0 Network deployment

[Rajesh Bhoir]

We have developed a client application which uses the JNDI context from the WAS 5.0 configuration. This client works fine when tested with a standalone (WAS 5.0 Single Server)
However when we tried to execute the same client on WAS 5.0 Network Deployment we are getting the following error. :roll:
C:\Program Files\WebSphere\AppServer\bin>LaunchClient storemsgsinqueue.ear
javax.naming.NameNotFoundException: jms/tpqcf
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.hsbc.newtp.common.ServiceLocator.lookup(ServiceLocator.java:91)
at com.hsbc.newtp.util.NewTPQueueHandler.<init>(NewTPQueueHandler.java:75)
at com.hsbc.newtp.simulator.mqs.StoreMsgsInQueue.<init>(StoreMsgsInQueue.java:71)
at com.hsbc.newtp.simulator.mqs.StoreMsgsInQueue.main(StoreMsgsInQueue.java:348)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)com.hsbc.newtp.common.TPTechnicalException
at com.hsbc.newtp.common.ServiceLocator.lookup(ServiceLocator.java:94)
at com.hsbc.newtp.util.NewTPQueueHandler.<init>(NewTPQueueHandler.java:75)
at com.hsbc.newtp.simulator.mqs.StoreMsgsInQueue.<init>(StoreMsgsInQueue.java:71)
at com.hsbc.newtp.simulator.mqs.StoreMsgsInQueue.main(StoreMsgsInQueue.java:348)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
I have check the "SystemOut.log" file for the server, and it shows that it has binded "jms/tpqcf".
Thanks
Rajesh
[ July 23, 2003: Message edited by: Rajesh Bhoir ]

[Kiran Kumar]

hi,
have u givent the Provider URL while creating the Initial Context.
this URL will be the server instance on which you want to access the JNDI tree.
hope this helps

[java id]

I'm also facing the same problem. Does anyone know the reason?

Thanks

[Jayadev Pulaparty]

Pls check the jndi port number you are passing while getting a reference to jndi InitialContext. Is it going to tbe same for singleServer and ND, i don't think so?

[java id]

My problem has got resolved. The scope for the JDBC provider was incorrect. The entry for node had to be modified and data sources were created.