| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuring JMS on WebSphere V5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| mail2aus |
 Posted: Tue Dec 09, 2003 4:21 am Post subject: Configuring JMS on WebSphere V5 |
 |
|
Newbie
Joined: 03 Nov 2003
Posts: 3
|
I am getting the following error when I tried to configure JMS (WebSphere Embedded JMS Server) on WebSphere Application Server V5 from the URL mentioned below..
http://www-06.ibm.com/developerworks/websphere/techjournal/0211_barcia/barcia.html#createMDB
[12/9/03 16:01:51:062 GMT+05:30] 6542ba21 MsgListenerPo W WMSG0049E: Failed to start MDB MyMDB against listener port MyMDBListenerPort
[12/9/03 16:01:51:078 GMT+05:30] 6542ba21 ApplicationMg A WSVR0221I: Application started: MDBTest
[12/9/03 16:01:51:141 GMT+05:30] 6542ba21 HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[12/9/03 16:01:54:453 GMT+05:30] 6542ba21 HttpTransport A SRVE0171I: Transport https is listening on port 9,443.
[12/9/03 16:01:54:484 GMT+05:30] 6542ba21 HttpTransport A SRVE0171I: Transport http is listening on port 9,090.
[12/9/03 16:01:54:766 GMT+05:30] 6542ba21 HttpTransport A SRVE0171I: Transport https is listening on port 9,043.
[12/9/03 16:01:54:844 GMT+05:30] 6542ba21 RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
[12/9/03 16:01:54:984 GMT+05:30] 6542ba21 WsServer A WSVR0001I: Server server1 open for e-business
[12/9/03 16:02:51:062 GMT+05:30] 58a17a2a MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: jms/MyMDBQueue
[12/9/03 16:02:51:078 GMT+05:30] 58a17a2a MDBListenerIm W WMSG0019E: Unable to start MDB Listener MyMDB, JMSDestination jms/MyMDBQueue : javax.naming.NameNotFoundException: jms/MyMDBQueue
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
The document explains the configuration for WebSphere Studio v5..
I have tried the same on WebSphere Application Server V5 instead of WebSphere Studio..
The JMS Listener has been successfully started ..
Can anybody please help me out on this ??
Austin |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 09, 2003 5:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| [12/9/03 16:02:51:062 GMT+05:30] 58a17a2a MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: jms/MyMDBQueue |
Did you create the Queue Destination in the WAS server, using the administration console? Is the JNDI name of that Queue destination exactly "jms/MyMDBQueue", with the same case?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
