This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Websphere and the fly likes WAS5.1 JMS configuration question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS5.1 JMS configuration question" Watch "WAS5.1 JMS configuration question" New topic
Author

WAS5.1 JMS configuration question

eric mcentee
Ranch Hand

Joined: May 02, 2001
Posts: 66
Hello-
I am migrating a Weblogic 7.0 app to WAS 5.1, and I'm just about there. However, I can't get my MDB's to start since I get the following error:
**************************
[1/6/04 11:06:41:679 EST] 3c1669d4 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource tpsQueueConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue
[1/6/04 11:06:41:694 EST] 3c1669d4 MDBListenerIm W WMSG0019E: Unable to start MDB Listener ErrorHandlerMsgBean, JMSDestination ErrorQueue : javax.jms.JMSException: MQJMS2008: failed to open MQ queue

**************************
There is more to the stack trace, I can include it if needed.
Anyway, I am using the built in Websphere JMS provider. I have set up my QueueConnection Factory, and my Queue Destinations. Some of my queues seem to work, but some get this.
I am able to start the individual listener ports from the admin console, but they stop when I try to restart the server with my application.
Has anyone run into something like this?
Thanks,
Eric
 
wood burning stoves
 
subject: WAS5.1 JMS configuration question
 
Similar Threads
MQJE001: Completion Code 2, Reason 2085
Failed to open Queue using MDB in WSAD using MQ Simulator (MQJMS2008)
WSAD5.1.3 remote MQv5.3 connection and listen using MDB
enlist failed while accessing MQ
JMS Issue with WAS 5.1