| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ 7.0 and WAS 6.1 connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| shavo25 |
 Posted: Mon Mar 23, 2009 7:34 pm Post subject: MQ 7.0 and WAS 6.1 connection |
 |
|
Apprentice
Joined: 16 Feb 2009
Posts: 29
|
I have an enterprise application (JEE1.4) running on WAS 6.1. I followed this tutorial:
http://www.ibm.com/developerworks/websphere/techjournal/0505_woolf/0505_woolf.html -- Make WebSphere MQ the JMS provider for applications deployed in WebSphere Application Server.
Now when i launch my j2ee client i can send/publish messages to the queue/topic and mdb prints out the messages to the log.
But when i stop the listener port for topic, send in a message and start the listener port again, i assume that my durable subscriber mdb will print out the message, but i am getting some weird excpetions around connecting to the queue manager on MQ.
Message : com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2002: Failed to get a message from destination 'SYSTEM.MANAGED.NDURABLE.49C1DF6F03FF0020'. WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.
Class : class com.ibm.msg.client.jms.DetailedInvalidDestinationException
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2052' ('MQRC_Q_DELETED').
In my admin console >> environment variables WAS_LIBS_DIR is pointing to the correct folder, inside that directory, i have my WMQ lib folder with three jars:
com.ibm.mq.jar, com.ibm.mqjms.jar and dhbcore.jar.
Should i overwrite these jar files with the ones from websphere MQ 7.0?
Or why is it that the queue seems to have been been deleted?
Actually another thing when i try in my admin console to test a connection to my websphere MQ server, i get the error:
*WebSphere MQ server Websphere MQ connection test failed for WebSphere MQ queue manager SHANEMGR. CWSJP0019E: An attempt to connect to WebSphere MQ using the information that is provided by the WebSphere MQ Server bus member SHANEMGR resulted in a connection to a WebSphere MQ queue manager running on version Unknown - 700 0x2bc on platform MQPL_WINDOWS_NT. This configuration is not supported. Destinations that are assigned to the WebSphere MQ Server bus member are not accessible..
*
Is this why i need the WMQ 7.0 jar files or is websphere application server 6.1 not compatiable with MQ 7.0? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 23, 2009 8:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is wrong with the picture of a durable subscriber going against a temporary queue or a dynamic queue? 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
