Error Code 2085
Contents |
2085 MQRC_UNKNOWN_OBJECT_NAME MQRC_UNKNOWN_OBJECT_NAME MQRC_UNKNOWN_OBJECT_NAME unknown object name Technote (troubleshooting) Problem(Abstract) Your WebSphere MQ application program fails with reason code 2085 (MQRC_UNKNOWN_OBJECT_NAME) when you attempt to open a queue. 2085 mqseries reason code 2085 0x00000825 MQRC UNKNOWN OBJECT NAME Cause This reason code is issued when an
Mqopen Ended With Reason Code 2085
application opens a queue, and the queue manager cannot resolve to a queue name specified in the MQOPEN object descriptor (MQOD).
Mqexception Mqje001 Completion Code 2 Reason 2085
The most likely reason is that a wrong queue name was specified on the MQOPEN API call. Resolving the problem Debugging techniques: If the queue is a locally defined queue: Verify that your program
Mq 2085 Reason Code 2
is connecting to the correct queue manager. Use the MQSC dis ql(*) command to determine if the target queue is defined. Make sure that your program specifies the correct queue name in the correct case. If the queue is a cluster queue: Same general rules as above. If you expect the MQOPEN to resolve to a cluster queue that is not locally defined, you must not specify the ObjectQMgrName mq reason code 2058 in the object descriptor (MQOD). 2085 may indicate WebSphere MQ cluster configuration problems. Ensure that the cluster queue managers have working channel connections to, and from the repository queue manager using: MQSC dis chs(*) command. Ensure that the queue is shared in the cluster using: MQSC dis ql(*) command. 2085 opening a cluster queue for input is not supported. Corrective actions Specify the correct queue name Define the queue Do not specify ObjectQMgrName in the object descriptor (MQOD) Resolve cluster channel issues Share the queue in the cluster Example: In this test we successfully put a message to target queue SVR.LQ. This works as expected. Notice what happens when we specify this same queue name in lower case. We fail with 2085. Related information WebSphere MQ Library A Japanese translation is available Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Express Capability Linux, Windows 5.3 Product Alias/Synonym WMQ MQ Document information More support for: WebSphere MQ Application / API Software version: 3.0, 5.3.1, 6.0, 6.0.2, 7.0, 7.0.1, 7.1, 7.5 Operating system(s): AIX, HP-UX, IBM i, Linux, OpenVMS, Solaris, Tandem NSK, VSE, Windows, z/OS Reference #: 1166940 Modified date: 2013-05-14 Site availability Site assistance Contact and feedback Need support? Submit
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 http://portal2portal.blogspot.com/2015/04/mqopen-ended-with-reason-code-2085.html 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 https://coderanch.com/t/320075/EJB-JEE/java/MQJE-Completion-Code-Reason 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 code 2 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) reason code 2 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 ESB.TO.BPM.CLQHello BPM from ESBSample AMQSPUT0 endwh
This Site Careers Other all forums Forum: EJB and other Java EE Technologies MQJE001: Completion Code 2, Reason 2085 V Singh Greenhorn Posts: 6 posted 9 years ago Hi, I am getting the following exception when I am trying to invoke a MDB through servlet.:- The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$MyMdbConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue [9/11/07 11:44:16:588 IST] 4dfb49e7 MDBListenerIm W WMSG0019E: Unable to start MDB Listener Hello, JMSDestination jms/MyMdbQueue : javax.jms.JMSException: MQJMS2008: failed to open MQ queue at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540) at com.ibm.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:460) at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271) at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:277) at com.ibm.mq.jms.MQConnectionBrowser.