Mq Error 2082
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » General IBM MQ Support » Error Code 2082 when resolving queue over cluster Error Code 2082 when resolving queue over cluster « View previous topic :: View next topic » Author Message hilltops Posted: Sat Jun 09, 2007 1:43 am Post subject: Error Code 2082 when resolving queue over cluster CenturionJoined: 01 Mar 2006Posts: 112 I am getting the error code 2082 (MQRC_UNKNOWN_ALIAS_BASE_Q) when trying to resolve a queue local over a cluster. My environment is set up as follows; I have got an MQ cluster with two queue managers QM_A http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q039210_.htm and QM_B. QM_B act as the gateway into the cluster and all connection must pass thru QM_B as this is where we implement our security checks. An application connection to QM_B over MQ client connection. This application is a 3rd party product over which we have no control. Messages arrive to a queue local on QM_B from QM_A. The application is design to poll this queue on QM_B and then send responses back to QM_A via a queue alias. Thus; QA(alias on QM_A for request) -----> http://www.mqseries.net/phpBB/viewtopic.php?p=181222&sid=e2d72f133074d0a9344619d7036d4d2d QL(clustered queue on QM_B for request) QL(clustered queue on QM_A for Resp) <--- QA(alias on QM_B for Resp) All queue objects are defined with the attribute DEFBIND(NOTFIXED). When the application tries to open the queue on QM_B, I get the error code 2082, suggesting that MQ is trying to resolve the target on the local queue manager, QM_B. However, this should be being resolved over the cluster to the QM_A. I suspect the application is opening the queue alias using code like this; MQQueue q = qmgr.accessQueue("QA on QM_B", openOption, "QM_B", null, null); I have tested this idea on a small sample application and I also get 2082. Has anyone come across this and found a solution around this problem. I know if I omit the QM_B in the method above it works, but for this application we have not access to the code. Thankx Back to top fjb_saper Posted: Sat Jun 09, 2007 5:24 am Post subject: Grand PoobahJoined: 18 Nov 2003Posts: 18635Location: LI,NY The response is best left without any aliases. The app on QM_B should just send the response to the qmgr and queue as stated in the reply to fields of the request. The requestor specifies the qmgr and queue name it wants the reply be sent to. This replyto queue does not need to be clustered. Cluster resolution will only come into play for the routing from QM_B to QM_A and should not play any role with the queue resolution. Remember the replyto queue could be a temporary dynamic queueQueue http://www.capitalware.com/rl_blog/?p=188 is a Bad Idea » Are you having MQ Cluster problems or issues? January 7, 2011 Roger Lacroix The following are links to solutions in the IBM WebSphere MQ documentation for particular problems / issues. A cluster sender channel is in retry state mq error http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13100_.htm DISPLAY CLUSQMGR command shows CLUSQMGR names starting SYSTEM.TEMP http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13120_.htm Applications get RC of 2035 (MQRC_NOT_AUTHORIZED) when trying to open a queue in the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13430_.htm Applications get RC of 2085 (MQRC_UNKNOWN_OBJECT_NAME) when trying to open a queue in the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13140_.htm Applications mq error 2082 get RC of 2189 (MQRC_CLUSTER_RESOLUTION_ERROR) when trying to open a queue in the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13160_.htm Messages are not appearing on the destination queues http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13180_.htm Application gets RC of 2082 (MQRC_UNKNOWN_ALIAS_BASE_Q) when opening a queue in the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13440_.htm Messages put to a cluster alias queue go to SYSTEM.DEAD.LETTER.QUEUE http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13200_.htm A queue manager does not appear to have up to date information about queues and channels in the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13220_.htm No changes in the cluster are being reflected in the local queue manager http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13240_.htm DISPLAY CLUSQMGR command shows a queue manager twice http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13260_.htm RESET CLUSTER and REFRESH CLUSTER commands were issued, but the queue manager would not rejoin the cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13280_.htm Out of date information in a restored cluster http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13310_.htm The cluster DEMO force removed by mistake http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13320_.htm