Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Enabling embedded messaging in WebSpeher 5.1

3 views
Skip to first unread message

msmolyak

unread,
Feb 15, 2006, 12:33:21 PM2/15/06
to
Hello,

I am trying to configure and test messaging using WebSphere 5.1 server. How do I tell whether the embedded JMS engine is installed on my server? Do I need to do anything special in the admin cosnole to start the JMS engine?

I am configuring a JMS connection factory and a queue destination through the console and trying to set up a listen port (for an MDB to use) using those objects. WebSphere complaints that it cannot start the listen port since the queue destination is not bound to JNDI. Since I have created it I would expect it to be in the JNDI tree.

What am I missing?

Michael

[2/15/06 11:42:07:603 EST] 1ad1a240 MDBListenerIm W WMSG0019E: Unable to start MDB Listener MessageReceiver, JMSDestination jms/JetsonQueueDestination : javax.naming.NameNotFoundException: Context: msmolyak_node/nodes/msmolyak_node/servers/server1, name: jms/JetsonQueueDestination: First component in name jms/JetsonQueueDestination 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.handleNameNotFound(WsnOptimizedNamingImpl.java:1983)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1320)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:2500)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.<init>(WsnOptimizedNamingImplBase.java:2965)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1423)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:3493)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1521)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1482)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1189)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1069)
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)

0 new messages