Mq Error Message 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 mq completion code 2 reason 2085 queue. 2085 0x00000825 MQRC UNKNOWN OBJECT NAME Cause This reason code is issued when mqopen ended with reason code 2085 an application opens a queue, and the queue manager cannot resolve to a queue name specified in the MQOPEN object mq reason code 2058 descriptor (MQOD). 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 mqopen failed with reason code 2085 your program 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
Websphere Mq Call Failed With Compcode 2 Mqcc_failed Reason 2085 Mqrc_unknown_object_name
not specify the ObjectQMgrName 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: 14 May 2013
by QueueManagerHost name configuration was app server
Failed To Open Queue. Reason Code 2085
Technote (troubleshooting) Problem(Abstract) You notice the following messages are mq 2019 logged if the Java Message Service (JMS) is unable to find the queue manager. The mqjms2008: failed to open mq queue queue manager name is based on the QueueManagerHost name. In general, the reason code 2085 means that the referenced queue could not be found http://www.ibm.com/support/docview.wss?uid=swg21166940 on the Queue Manager. This specific issue, however, 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. http://www-01.ibm.com/support/docview.wss?uid=swg21245036 The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue [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
a JMS Provider in Clustered Configurations Technote (troubleshooting) Problem(Abstract) When the user tries to deploy an event project, they see the following errors http://www-01.ibm.com/support/docview.wss?uid=swg21516881 - "Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME') in WAS SystemOut.log. Symptom After running the configure_MQ_JMS_messaging.py script on WAS side and also the http://www.webspheretools.com/sites/webspheretools.nsf/docs/MQOPEN%20ended%20with%20reason%20code%202085 MQJMS_PSQ.mqsc on MQ side, they are able to start the server. However, when they try to deploy an event project, they see errors - Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call code 2 failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME'). Another error message similar to the following is also seen: [9/19/11 14:57:26:860 CDT] 0000002a ActivationSpe E J2CA0138E: The Message Endpoint activation failed for ActivationSpec jca/wbe_history (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB application wberuntimeear#wberuntime.jar#HistoryModule due to the following exception: com.ibm.mq.connector.DetailedResourceException Cause The exception indicates an attempt to access a queue on an MQ queue manager. The queue, does not reason code 2085 exist on that queue manager. To verify, run runmqsc command on the system where the queue manager is running: runmqsc QMGR_NAME dis q(
06-Apr-2009 Related Document Categories: Get my WebSphere MQ course here >> http://www.themiddlewareshop.com/products/ MQOPEN ended with reason code 2085 -bash-3.00$ /opt/mqm/samp/bin/amqsput LQ.Test TSTDADQ1 Sample AMQSPUT0 start target queue is LQ.Test MQOPEN ended with reason code 2085 unable to open queue for output Sample AMQSPUT0 end Thee reason is the queue is called LQ.TEST not LQ.Test Get my WebSphere MQ course here >> http://www.themiddlewareshop.com/products/ About Me Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware. In January 2013, I was awarded the prestigous 'IBM Champion' accolade. Linked In Twitter About Me My Blog Contact Me Read my books? IBM WebSphere Application Server 8.0 Administration Guide WebSphere Application Server 7.0 Administration Guide WebSphere Blog Recent Articles All Articles WebSphere Categories WebSphere Consultant WebSphere Application Server WebSphere Message Broker WebSphere MQ Jython JACL Install Rational Other Categories Shell Scripts Java Consultant Java Sample Code JMS MBeans Tomcat Clustering & Load balance> Websphere Tips Eclipse Contact | Articles | Shell Scripts | Java Code | JACL | Jython | WebSphere MQ | WebSphere Message Broker | WebSphere Blog | © Copyright 2006-2013 Robinson (UK) Limited