ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Unable to lookup JMS resources, JNDI lookup exception:

Post new topic  Reply to topic
 Unable to lookup JMS resources, JNDI lookup exception: « View previous topic :: View next topic » 
Author Message
milind
PostPosted: Wed Jul 21, 2004 7:14 pm    Post subject: Unable to lookup JMS resources, JNDI lookup exception: Reply with quote

Newbie

Joined: 29 Jan 2003
Posts: 6
I am getting the following error
WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception:
When i startup my WAS.
1. I have a message driven bean and i am using the MQ as JMS provider.
2. The application works fine when i testded under WSAD 5.1 test server.
3. Now i am trying to install it on NT or AIX server through the Admin Console and getting the trouble installing it .
4. I am using the file system URL.
5. In the WAS consloe i setup Generic JMS provider and also the listener port.
Everyhting running fine under WSAD 5.1 test server. Now when i am trying to install it on WAS 5.0 i am getting above error.
Please help me figure out this as its very urgent. Here is the exception.
[7/21/04 20:18:09:203 EDT] 64f6abb2 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: jms/OSSC_MQ_Q
[7/21/04 20:18:09:297 EDT] 64f6abb2 MDBListenerIm W WMSG0019E: Unable to start MDB Listener OsscMDB, JMSDestination jms/OSSC_MQ_Q : javax.naming.NameNotFoundException: jms/OSSC_MQ_Q
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.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:404)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:437)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:144)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:660)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:631)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:139)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:371)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:726)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:139)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:135)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:542)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:254)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:232)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:117)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jul 22, 2004 5:17 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
This is not a questions about MQSeries with Java or JMS.

It is a WAS and MQSeries setup question. Have you considered asking your WAS Administrator?

The exception you posted is not the exception that tells you what is broken and what needs to be fixed.

You need to find the exceptions that occurred during JNDI namespace binding during WAS startup.

This will be well before your applications are loaded, so look earlier in your log.

But if you want to use MQ as your JMS transport, then you should use the "Websphere MQ JMS Provider" and not the "Generic JMS provider" or the "WebSphere JMS Provider".
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
bower5932
PostPosted: Thu Jul 22, 2004 6:58 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
My guess is that you don't have the names spelled correctly between what you have setup on your ListenerPort and what you actually defined in your destination. You should see some messages at AppServer startup that shows what names got bound into the namespace.

And you should definitely use WebSphere MQ JMS Provider for resource definitions related to WebSphere MQ. You can use Generic, but you'll be responsible for things that are already done for you with WMQ.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
OmPat
PostPosted: Thu Jul 22, 2004 9:47 am    Post subject: Reply with quote

Apprentice

Joined: 20 Jul 2004
Posts: 33
Location: Charlotte
Milind,
Do you have Websphere MessagingClient.jar on your classpath. You need to have that for JNDI lookup. Otherwise the JNDI look up does not get the right context and the look up fails.
You can also use DUMPNAMESPACE command available in /bin of Wepsphere directory to see if your context definitions are correct.
Hope this helps you.
_________________
IBM Certified WMQ V5.3 System Administrator
IBM Certified WMQ V5.3 Solutions Designer
Brainbench Certified MQ Expert
IBM Certified WMQI V2.1 Solutions Expert
IBM Certified WMQI V2.1 Specialist
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Unable to lookup JMS resources, JNDI lookup exception:
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.