jQuery in Action, 3rd edition
The moose likes Websphere and the fly likes Exception in JMS due to Configuration. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Customer Requirements for Developers this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Exception in JMS due to Configuration." Watch "Exception in JMS due to Configuration." New topic

Exception in JMS due to Configuration.

balaji anatha padmanaban

Joined: Jun 18, 2008
Posts: 19

I am using IBM websphere server6.0.2.17 and sonicMQ Messageing servie for JMS part.
I configured queues one is for getting the messeage and sending the message.I have configured my queues in Generic part in JMS provider and Lister port in server.
This request Queue I made a JNDI name in Generic part in JMS provider part and configured in Listener port with same JNDI name as jms/IdidRequestRef.
There are two servers in my APP severs.I configured ite listener port in two server nodes also.

Please give some solution.
I am getting exception like

WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: IDL m
[10/2/08 3:35:50:578 CDT] 00000032 MDBListenerIm W WMSG0019E: Unable to start MDB Listener IdisMDB, JMSDestination jms/Idis
RequestRef : javax.naming.NameNotFoundException: Context: picsteaDEV/clusters/PIEDEVcluster, name: jms/IdisRequestRef: First
component in name IdisRequestRef not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/C
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:543)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2213)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4043)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1746)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1412)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1290)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:145)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:234)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:726)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:699)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:1034)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
---- Begin backtrace for Nested Throwables

I agree. Here's the link: http://aspose.com/file-tools
subject: Exception in JMS due to Configuration.
It's not a secret anymore!