Unable to lookup JMS resources NotFound in WAS

[Sam Gehouse]

I am configuring MDB (Message Driven Bean) for a simple P2P application in WAS 5.1.x.

I have configured QueueConnectionFactory, Queue and MessageListener port and checked names etc.

Same configuration works in WSAD test server and I configured it in server level in WSAD.

However, I get following error in WAS (configured in nodes level):

Unable to lookup JMS resources, JNDI lookup exception: IDL mg.org/CosNaming/NamingContext/NotFound:1.0

[11/28/05 10:42:11:040 EST] 26559f1b MDBListenerIm W WMSG0019E: Unable to start MDB Listener ArchIngest, JMSDestination jms/TRD.OBD_ARCH_RPT.QL :

javax.naming.NameNotFoundException: Context: bnwspa02d/nodes/bnlj2eaa/servers/eResends_digest, name: jms/TRD.OBD_ARCH_RPT.QL: First component in name TRD.OBD_ARCH_RPT.QL not found.

Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0

at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:968)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1399)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:3491)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1519)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1067)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:218)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:586)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:560)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:878)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)

I have configured in nodes level in WAS.

Any help?

[Scott Selikoff]

When in doubt with a JNDI error, try using the JNDI explorer and verify the queue can be found that way before attempting to access in the application. Sorry, best I can help you with this one.

[Omkar Puli]

were you able to resolve this ? i have similar problem and would like to get your feedback

[Henry Wong]

Omkar Puli wrote:i have similar problem and would like to get your feedback

Basically, JNDI for Websphere is not configured by default -- so when you encounter such an error, it may be a good idea to talk to your Websphere administrator. My administrator fixed it, the last few times that this happened.

[Tim Holloway]

Henry Wong wrote:

Omkar Puli wrote:i have similar problem and would like to get your feedback

Basically, JNDI for Websphere is not configured by default -- so when you encounter such an error, it may be a good idea to talk to your Websphere administrator. My administrator fixed it, the last few times that this happened.

Surely that cannot be literally true. JNDI is an essential JEE service. You cannot locate a database connection pool without it. Every JEE webapp has a distinct JNDI space.

I think that more accurately, JMS probably needs to be configured and registered properly within WAS and possibly the application deployment.

[Henry Wong]

Tim Holloway wrote:I think that more accurately, JMS probably needs to be configured and registered properly within WAS and possibly the application deployment.

I don't know why IBM has the option to use JMS APIs without JNDI -- perhaps it is because many of their customer apps don't use Java. Regardless, you may be correct, in that JMS may also not be configured and registered properly. Working with Websphere has always been an area that I depended on an Administrator for...  

[Tim Holloway]

I've only ever worked with WebSphere where I was running WebSphere locally, so I'm not up on the finer points.

JMS is literally Java Messaging Services, though, so I have doubts about it having non-Java interfaces. I believe that, barring product name changes, JMS on WebSphere is actually supported by WebSphere MQ. I'm way out of date on that stuff, though.

[Paul Clapham]

Tim Holloway wrote:JMS is literally Java Messaging Services, though, so I have doubts about it having non-Java interfaces. I believe that, barring product name changes, JMS on WebSphere is actually supported by WebSphere MQ. I'm way out of date on that stuff, though.

That sounds true and I speak from my vast (or perhaps half-vast) experience as a WebSphere administrator. Although that would have been about the time of the original post (WebSphere 5!) and fortunately IBM Support worked reasonably well to fill in the (also vast) gaps.