Reason 2085 Mq Error
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
Mq Completion Code 2 Reason 2085
2085 (MQRC_UNKNOWN_OBJECT_NAME) when you attempt to open a queue. 2085 0x00000825 mq reason code 2085 while trying to open a queue MQRC UNKNOWN OBJECT NAME Cause This reason code is issued when an application opens a queue, and the
Mqopen Ended With Reason Code 2085
queue manager cannot resolve to a queue name specified in the MQOPEN object descriptor (MQOD). The most likely reason is that a wrong queue name was specified on the mq error code 2058 MQOPEN API call. Resolving the problem Debugging techniques: If the queue is a locally defined queue: Verify that 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 mq 2019 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 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 WebSphe
with WMQ V6
Mqopen Failed With Reason Code 2085
mqminfo; MQJMS2006; 2085; MQJMS_PQS.MQSC com.ibm.mq.MQException 2085 javax.jms.JMSException MQJMS2006 0x00000825 mqjms2008: failed to open mq queue MQRC_UNKNOWN_OBJECT_NAME SYSTEM.JMS.MODEL.QUEUE Technote (troubleshooting) Problem(Abstract) Your WebSphere MQ (WMQ) V6 (or earlier) JMS
Websphere Mq Call Failed With Compcode 2 Mqcc_failed Reason 2085 Mqrc_unknown_object_name
client application could not connect to WebSphere MQ queue manager. You get the following errors when creating the topic connection: com.ibm.mq.MQException: Completion http://www.ibm.com/support/docview.wss?uid=swg21166940 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 SYSTEM.JMS.MODEL.QUEUE http://www-01.ibm.com/support/docview.wss?uid=swg21174885 queue. Resolving the problem Create the WebSphere MQ system object definitions using the script called 'MQJMS_PSQ.MQSC,' (location:
a JMS Provider in Clustered Configurations Technote (troubleshooting) http://www-01.ibm.com/support/docview.wss?uid=swg21516881 Problem(Abstract) When the user tries to deploy an event project, http://www-01.ibm.com/support/docview.wss?uid=swg21566516 they see the following errors - "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 MQJMS_PSQ.mqsc on MQ code 2 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 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 reason code 2085 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 exist on that queue manager. To verify, run runmqsc command on the system where the queue manager is running: runmqsc QMGR_NAME dis q(
network timeout ETIMEDOUT MQJMS2007 2085 MQRC_UNKNOWN_OBJECT_NAME 2009 MQRC_CONNECTION_BROKEN keepalive TCP INTERVAL KAINT heartbeat hbint network timeout CSQX259E AMQ9259 mqminfo Technote (troubleshooting) Problem(Abstract) A JMS application successfully accessed a WebSphere MQ (WMQ) queue. After two or so hours, it received MQJMS2007 Completion Code 02 and reason code 2085. Cause Here is the sequence of events: The application created JMS connection and session objects. This resulted in a connection to WMQ for each session object, as most work is performed against the session. A temporary dynamic queue was created. For JMS, temporary queues should remain for the life of the JMS connection object. To achieve this in WMQ, a separate connection was created to the queue manager (a new SVRCONN channel instance with its own TCP/IP socket). A temporary dynamic queue (for example, AMQ.C7E4D882693BC507) was created using this SVRCONN. The JMS sessions performed more work over their own channel instances (including putting to the temporary queue). After some unknown period of time, the TCP/IP connection for the JMS connection described in step 2 above was broken. This is likely to have happened because no further work occurred on that channel, and some component of the network, such as a firewall, chose to time out the connection. Neither the client nor the MQ server detected this failure immediately. On the server, the channel was waiting for more requests from the client, using a TCP/IP receive call. After 2 hours, the keepalive value for the socket (from the system default) caused a probe packet to be sent to test that the TCP/IP connection was still valid. This failed, and the queue manager was notified that the connection was broken. The queue manager ended the channel with CSQX259E (z/OS) or AMQ9259 (distributed), and cleaned up the resources owned by the channel. This caused the temporary queue to be deleted. The client detected the broken connection in one of two ways: a) Trying to put a message to the temporary queue by way of another channel instance. Since the temporary dynamic queue no longer existed, this failed with 2085 (MQRC_UNKNOWN_OBJECT_NAME). b) Trying to create a new temporary queue. This attempted to use t