Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Unable to lookup JMS resources NotFound in WAS

 
Sam Gehouse
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
author
Saloon Keeper
Posts: 4028
18
Eclipse IDE Flex Google Web Toolkit
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic