| Author |
Unable to lookup JMS resources NotFound exception
|
|
|
| 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:omg.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:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl. do_resolve_complete_info(WsnOptimizedNam
ingImpl.java:968)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase. resolve_complete_info(WsnOptimizedNaming
ImplBase.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?
| |
| David Currie 2005-11-29, 7:51 am |
| Is this ND? A common mistake is to define the resources on the
deployment manager node rather than the application server node.
Regards,
David
| |
|
| a few thoughts:
1) sometimes the WAS needs to be restarted after your JMS changes are saved
2) verify your MessageListener port is active; it must be "started"
3) did you also go to the Server Components -> JMS Server and add your new Queue(s) to the list of names which the server starts & listens? while your there, verify the server defaults its queues to "started"
| |
|
| Did you use the correct version of MQ client jar? Make sure to setup the MQ_INSTALL_ROOT in the WAS varibles. Also you must upgrade the MQ server to version 6.0.2 if you are using MQ 6.0.0. Finally make sure the jndi name in your port defination is exactl
y the same as defined. See this:
http://lastbit.blogspot.com/2007/02...here-mq-v6.html
|
|
|
|