Ibm Mq Error Code 2085
Contents |
by QueueManagerHost name configuration was app server Technote (troubleshooting) Problem(Abstract) You mq 2019 notice the following messages are logged if the Java Message Service failed to open queue. reason code 2085 (JMS) is unable to find the queue manager. The queue manager name is based on
Mqjms2008: Failed To Open Mq Queue ''.
the QueueManagerHost name. In general, the reason code 2085 means that the referenced queue could not be found on the Queue Manager. This specific issue, however, http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q039190_.htm is caused by the configured QueueManagerHost. SystemOut.log [7/22/05 10:23:24:237 EDT] 7b40fe EJBContainerI I WSVR0037I: Starting EJB jar: CMSReportsBusiness.jar [7/22/05 10:23:26:756 EDT] 7b40fe ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$cms_queue_factory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue http://www-01.ibm.com/support/docview.wss?uid=swg21245036 [7/22/05 10:23:27:154 EDT] 7b40fe MDBListenerIm W WMSG0019E: Unable to start MDB Listener InterfaceProcessor, JMSDestination jms/cms_interface_queue : javax.jms.JMSException: MQJMS2008: failed to open MQ queue at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironme nt.java:540) at com.ibm.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:460) at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271) An MQJMS2008 exception with Reason Code 2085 when WebSphere Application Server attempts to start the "ReceiverListenerPort" listener port. Reason Code 2085 typically indicates that the queue doesn't exist on the queue manager that the application is connected to. Resources.xml
with WMQ V6 http://www-01.ibm.com/support/docview.wss?uid=swg21174885 mqminfo; MQJMS2006; 2085; MQJMS_PQS.MQSC com.ibm.mq.MQException 2085 javax.jms.JMSException MQJMS2006 0x00000825 MQRC_UNKNOWN_OBJECT_NAME SYSTEM.JMS.MODEL.QUEUE Technote (troubleshooting) Problem(Abstract) Your WebSphere MQ (WMQ) V6 (or earlier) JMS http://portal2portal.blogspot.com/2015/04/mqopen-ended-with-reason-code-2085.html client application could not connect to WebSphere MQ queue manager. You get the following errors when creating the topic connection: com.ibm.mq.MQException: code 2 Completion Code 2, Reason 2085 javax.jms.JMSException: MQJMS2006: MQ problem: com.ibm.mq.MQException: Completion Code 2, Reason 2085 Symptom 2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME Cause A WMQ trace of the failure shows that one of your WMQ system queues is missing. In this particular case, it was the reason code 2 SYSTEM.JMS.MODEL.QUEUE queue. Resolving the problem Create the WebSphere MQ system object definitions using the script called 'MQJMS_PSQ.MQSC,' (location:
is a repository of the stuff that I learn, play with, enjoy and want to share. If you follow one of my tips, your mileage MAY well vary - Here be dragons :-) Thursday, 9 April 2015 MQOPEN ended with reason code 2085 - WebSphere MQ and Clustered Queues I hit this problem earlier today: -/opt/ibm/mqm/usr/mqm/samp/bin/amqsput ESB.TO.BPM.CLQ ESB1.DEV1Sample AMQSPUT0 starttarget queue is ESB.TO.BPM.CLQMQOPEN ended with reason code 2085unable to open queue for outputSample AMQSPUT0 endI could see the queue on the Queue Manager local to where I was running the command ( my ESB box, running IIB 9 and MQ 8 ).However, when I looked more deeply: -display queue(ESB*) 1 : display queue(ESB*)AMQ8409: Display Queue details. QUEUE(ESB.TO.BPM.CLQ) TYPE(QLOCAL)display queue(ESB.TO.BPM.CLQ) 2 : display queue(ESB.TO.BPM.CLQ)AMQ8409: Display Queue details. QUEUE(ESB.TO.BPM.CLQ) TYPE(QLOCAL) ACCTQ(QMGR) ALTDATE(2015-04-07) ALTTIME(13.28.28) BOQNAME( ) BOTHRESH(0) CLUSNL( ) CLUSTER(UAT1) CLCHNAME( ) CLWLPRTY(0) CLWLRANK(0) CLWLUSEQ(ANY) CRDATE(2015-04-07) CRTIME(13.28.28) CURDEPTH(0) CUSTOM( ) DEFBIND(NOTFIXED) DEFPRTY(0) DEFPSIST(YES) DEFPRESP(SYNC) DEFREADA(NO)….I could immediately see the problem ….The cluster to which I was expecting the Queue to belong was called DEV1and yet the CLUSTER() value above was set to UAT1.I verified this: -display CLUSQMGR(*) 5 : display CLUSQMGR(*)AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(LRPO1.DEV1) CHANNEL(DEV1.LRPO1.DEV1) CLUSTER(DEV1)AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(REP1.DEV1) CHANNEL(DEV1.REP1.DEV1) CLUSTER(DEV1)AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(REP2.DEV1) CHANNEL(DEV1.REP2.DEV1) CLUSTER(DEV1)which confirmed that the cluster name should indeed be DEV1.I changed the Queue definition: -alter qlocal(ESB.TO.BPM.CLQ) cluster(DEV1)and re-tested: -/opt/ibm/mqm/usr/mqm/samp/bin/amqsput ESB.TO.BPM.CLQ ESB1.DEV1it responded as I'd expected: -Sample AMQSPUT0 starttarget queue is E