Mq Error Code 2033
Contents |
AVAILABLE Technote(トラブルシューティング) 問題(概要) WebSphere MQ (WMQ)アプリケーションでキューからメッセージをゲットするときに、下記のリターンコードで失敗することがあります。 症状 2033 0x000007f1 MQRC_NO_MSG_AVAILABLE 原因 以下は、MQ理由コード 2033 の最も考えられる原因です。 -キューにメッセージがない -MQPUTの作業単位(Unit of Work(UOW))がコミットされなかった mq reason code -メッセージの有効期限が切れた 診断 ・この理由コードを通常の状態と考え、アプリケーションでこの状況をハンドルするようにしてください。 MQGET MQGMO_WAIT オプションを利用して、MQGET を使用することで対応できます。 (amqsget のサンプルプログラムでMQGET MQGMO_WAIT オプションを使用していますので、参照ください。) ・メッセージをPUTしているアプリケーションが、作業単位(UOW)ごとにコミットをしているかどうか確認してください。CurrentDepthはMQPUTが発行されるごとに増えていきますが、それらのメッセージがコミットされるまで、MQGETを発行するアプリケーションはそれらのメッセージをGETすることができません。 ・有効期限が切れたメッセージも、CurrentDepthにカウントされます。それら有効期限切れのメッセージはMQGETのタイミングで破棄されます。期限切れのメッセージは、アプリケーションでGETできません。メッセージの有効期限を増やすか、無期限にすることを検討ください。 *MQRC 2033は、多くの理由があります。この文書は、最も一般的な原因を記述しています。 WebSphere MQ Application Programming Referenceは、MQ機能呼び出しとReturnコードのリストに関して情報を提供しています。 【関連文書】 WebSphere MQ : The Get sample programs 2033 (07F1) (RC2033): MQRC_NO_MSG_AVAILABLE 英文:Technote (FAQ) : 1232330 2033 MQRC NO MSG AVAILABLE ※ 最新の情報は英文をご参照いただくことをお勧めいたします。 【お問合せ先】 技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 IBM サービス・ライン Document information More su
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss mqrc_no_msg_available c# the workings and policies of this site About Us Learn more about mq reason code 2018 Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow mq timeout error 2033 Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each http://www.ibm.com/support/docview.wss?uid=swg21640862 other. Join them; it only takes a minute: Sign up How to avoid MQRC2033 NO_MSG_AVAILABLE up vote 4 down vote favorite 1 I have a simple program to process messages from a queue. My intention is to process all available messages in queue and still listen to queue for incoming messages. I have written the processing part inside http://stackoverflow.com/questions/6479259/how-to-avoid-mqrc2033-no-msg-available a infinite loop as i want it to listen to queue always and process messages. Once after processing all messages again it tries to get a message(as it is inside a infinite loop) from the queue and there is no messages it throws MQRC 2033 NO_MSG_AVAILABLE exception(infact it is correct) and my program exits. Can someone give an idea to continously listen to this queue and avoid this exception. websphere-mq share|improve this question asked Jun 25 '11 at 17:06 Vignesh 3281431 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted When you execute the MQGET API call, there is an option to have the program wait for messages. You can specify a wait time (in milliseconds) or specify to wait forever. Just make sure that if you have the app wait for more than a few seconds, also specify 'Fail if Quiescing'. This allows the queue manager to be stopped cleanly. Without 'Fail if Quiescing' the administrator will need to issue a preemptive shutdown which can
Certification Databases Caching Books Engineering Languages Frameworks Products This Site Careers Other all forums Forum: WebSphere Problem reading mesage from MQ - https://coderanch.com/t/583361/Websphere/reading-mesage-MQ 2033 Yogesh Gandhi Ranch Hand Posts: 226 posted 4 years ago I am facing a problem when reading from a MQ queue. I have written two functions: public http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1867354.aspx String readRequestMQMessage(String xmlRequestID) //throws MQException, Exception { return readMQMessage(xmlRequestID, outputRequestQueueName); } public String readEnquiryMQMessage(String xmlRequestID) //throws MQException, Exception { return readMQMessage(xmlRequestID, outputEnquiryQueueName); } Only difference in the two code 2 functions is that queueName is being changed (which is being passed as a parameter) . But I get a message 2033 when reading from Enquiry Queue, while the same code works perfectly fine in case of Request Queue. Can anyone give me a clue, what could be the possible reason for such a behavior. The function readMQMessage uses mq reason code the following options: int intoptionForOutputQueue = MQC.MQOO_INPUT_AS_Q_DEF | MQC.MQOO_OUTPUT; getMsgOptionsMq = new MQGetMessageOptions(); getMsgOptionsMq.options = MQC.MQGMO_SYNCPOINT; //8195; getMsgOptionsMq.matchOptions = MQC.MQMO_MATCH_CORREL_ID; MQEnvironment.hostname = MQHostname; MQEnvironment.channel = channelName; MQEnvironment.port = Integer.parseInt(MQPortname); MQEnvironment.properties.put("transport", "MQSeries Client"); outMQueue = qManager.accessQueue(outputQueueName, intoptionForOutputQueue, null, null, null); MQMessage retrievedMsg = new MQMessage(); retrievedMsg.correlationId = correlationByte; outMQueue.get(retrievedMsg, getMsgOptionsMq); Yogesh Gandhi Ranch Hand Posts: 226 posted 2 years ago At last I had to use browseEnquiryMessage method to read all the messages present in the queue. (That worked). This worked for me, I don't know the reason, but I was able to get rid of my problem. /* * This function iterates over all the present messages * in the Enquiry queue, creates an arrayList of all the messages * and returns the arrayList. * Also, this function will delete the message after * it reads the message from the queue. */ public ArrayList
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Missing MQ Metrics with Reason Code 2033 Document ID:TEC1867354 Last Modified Date:12/07/2015 {{active ? 'Hide' : 'Show'}} Technical Document Details Products CA Application Performance Management Releases CA Application Performance Management:Release:9.5.2 Components WILY INTROSCOPE:APMINT Issue: Customer's MQ Metrics are grayed out in the Investigator. In the MQ Agent.log we found an ERROR with a Reason Code 2033. After research we found that on the customers Queue Manager's Command Server was not functioning. The customer restarted the Command Server and recycled the agents and all the metrics were available again. Environment: IBM Websphere MQand APM EM version 9.5.2 (This KB should be true for all versions of APM) Cause: [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.TracerDriverThread] MQMonitor: For configuration instance PAMQFLD001 and the drivers(namelist,cluster) an error occured in sending query to MQ. The target MQ (pamqfld001.thrivent.com:5102) may be down. Reason code 2033 MQRC_NO_MSG_AVAILABLE - for the logs. This error is telling you that the agent can't communicate with Queue Manager. Here is key information from the APM for IBM WebSphere MQ Guide about the Command Server: Verify Server Connection and Access To ensure proper server connection, verify the following: � A WebSphere MQ command server that is defined and running on the Queue Manager. � A Server Connection channel that is defined on the Queue Manager. Note: Contact your WebSphere MQ specialist for details about configuring the Queue Manager. � Network access through firewalls, for the MQ Monitor Agent. Resolution: Work with the MQ Administrator to make sure the Command Server is running correctly. Please h