aspose file tools*
The moose likes Websphere and the fly likes JMS ---- URGENT !!!! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "JMS ---- URGENT !!!!" Watch "JMS ---- URGENT !!!!" New topic
Author

JMS ---- URGENT !!!!

Soman Singh
Ranch Hand

Joined: Sep 02, 2003
Posts: 37
Hi All,
I was trying a simple example of JMS on wsad 5.1.
I nearly tried all the possibilities and don't really know i get those error.
I also installed the IBM embeded MQ. I get the following errors when i run the server ::

[9/2/04 15:34:38:378 IST] 3cec3270 WebGroup I SRVE0180I: [MDBTestWeb] [/MDBTestWeb] [Servlet.LOG]: InvokerServlet: init
[9/2/04 15:34:38:472 IST] 3cec3270 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
[9/2/04 15:34:38:503 IST] 3cec3270 MDBListenerIm W WMSG0019E: Unable to start MDB Listener MyMDB, JMSDestination MyMDBQueue : javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: MyMDBQueue: First component in name MyMDBQueue 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:1398)
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:132)
at javax.naming.InitialContext.lookup(InitialContext.java:360)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:215)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:553)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:485)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:443)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:152)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:666)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:637)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:139)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:388)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:770)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:156)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:152)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:586)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:271)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:249)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)

[9/2/04 15:34:38:535 IST] 3cec3270 MsgListenerPo W WMSG0049E: Failed to start MDB MyMDB against listener port MyMDBListenerPort
[9/2/04 15:34:38:550 IST] 3cec3270 ApplicationMg A WSVR0221I: Application started: MDBTest
[9/2/04 15:34:38:660 IST] 3cec3270 HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[9/2/04 15:34:40:957 IST] 3cec3270 HttpTransport A SRVE0171I: Transport https is listening on port 9,443.
[9/2/04 15:34:41:003 IST] 3cec3270 HttpTransport A SRVE0171I: Transport http is listening on port 9,090.
[9/2/04 15:34:41:425 IST] 3cec3270 HttpTransport A SRVE0171I: Transport https is listening on port 9,043.
[9/2/04 15:34:41:550 IST] 3cec3270 RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
[9/2/04 15:34:41:675 IST] 3cec3270 WsServer A WSVR0002I: Server server1 open for e-business, problems occurred during startup
[9/2/04 15:35:38:535 IST] 538df272 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
[9/2/04 15:35:38:551 IST] 538df272 MDBListenerIm W WMSG0019E: Unable to start MDB Listener MyMDB, JMSDestination MyMDBQueue : javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: MyMDBQueue: First component in name MyMDBQueue 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:1398)
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:132)
at javax.naming.InitialContext.lookup(InitialContext.java:360)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:215)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:553)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:527)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:809)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)




and many more.

The probs seems in the look up. I checked the names for look and they are consistent.
I was trying the example with URL:
http://www-106.ibm.com/developerworks/websphere/techjournal/0211_barcia/barcia.html#configtestMDB

If anyone has tried the same before and was successful in running the apps... plz let me know.

Thx in advance ...
sos
Pal andy
Greenhorn

Joined: Sep 10, 2004
Posts: 11
Hi,

Even I am facing the same problem. If you know the solution, please let me know.
Any help is appreciated.
Roland Barcia
author
Ranch Hand

Joined: Apr 15, 2004
Posts: 177
This article should help out, the article you are looking at is from a early availabity edition. Try this article for configuration help:

http://www-106.ibm.com/developerworks/websphere/library/techarticles/0310_barcia/barcia.html


Roland Barcia<br />STSM - ISSW Lead Web 2.0 Architect
 
Don't get me started about those stupid light bulbs.
 
subject: JMS ---- URGENT !!!!
 
Similar Threads
DataSource lookup problem from WebSphere 5.1 Stand alone Client Program
J2CXAResource E J2CA0036E: Error in WSAD v5.0
Exception in JMS due to Configuration.
Unable to lookup JMS resources NotFound in WAS
WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: jms/MyMDBQueue