Mq Error Code 2042
Contents |
PREVIOUSLY FAILED WITH UNEXPECTED ERROR, HOLDING THE OBJECT HANDLE OPEN. Fixes are available WebSphere MQ V7.0 for i5/OS Fix Pack 7.0.0.1 WebSphere MQ V7.0 for i5/OS Fix
Completion Code 2, Reason 2042
Pack 7.0.0.2 WebSphere MQ V6.0 Fix Pack 6.0.2.4 WebSphere MQ V7.0 Fix Pack websphere mq error 2042 7.0.0.1 WebSphere MQ V7.0 Fix Pack 7.0.0.2 WebSphere MQ V7.0 Refresh Pack 7.0.1.0. WebSphere MQ V7.0 Fix Pack 7.0.1.1 WebSphere
Mqrc 2042
MQ V7.0.1 for i5/OS Fix Pack 7.0.1.1 WebSphere MQ V7.0 Fix Pack 7.0.1.2 WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.2 WebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.7 WebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.10 (FP03) Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description Suppose a MQ application gets disconnected abnormally from the queue manager, due to unexpected error from a MQ API, while having handles to queues still open. In such a scenario, if the application disconnects and reconnects to the queue manager (rather than terminating the process) then the connection should get re-established and the queue manager operation should continue normally. This, however, is not currently the case, when the application disconnects from the queue manager after receiving MQRC_UNEXPECTED_ERROR then the disconnect is not being fully processed, and then when the application reconnects to the queue manager then it can find that locks held by the previous instance of the application prevent it from running correctly. This might manifest itself as an MQRC_OBJECT_IN_USE (2042), or a message being locked by a browse cursor or a transaction. For example, if a MQ-XA application fails in MQBEGIN or MQCMIT with MQRC_UNEXPECTED_ERROR, and the application then disconnects from the queue manager. Suppose this application had a handle to one of the queue objects open with MQOO_INPUT_EXCLUSIVE when it received the MQRC_UNEXPECTED_ERROR. If the application then reconnects to the queue manager, a subsequent MQOPEN call on the same queue object, again with MQOO_INPUT_EXCLUSIVE, fails with MQRC_OBJECT_IN_USE. The application then has to be restarted in order to recover from the failure. Local fix NA Problem summary **************************************************************** USERS AFFECTED: Applications having handles to queue objects open with MQOO_INPUT_EXCLUSIVE when disconnected
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » General IBM MQ Support » reason code 2042 reason code 2042 « View previous topic :: View next topic » Author Message chris boehnke Posted: Mon Nov 09, 2009 11:45 am Post subject: reason code 2042 PartisanJoined: 25 Jul 2006Posts: 369 Hi Guys, We have our application getting messages from a Mainframe queue manager. When they try getting messages they are http://www.ibm.com/support/docview.wss?uid=swg1IZ12208 getting 2042 reason code. I checked the MQ Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error. MQ version 6.0.2.0, z/OS can you guys throw some light on this. Back to top Vitor Posted: Mon Nov 09, 2009 12:17 pm Post subject: Re: reason code 2042 Grand High PoobahJoined: 11 Nov 2005Posts: 23698Location: Ohio, USA chris boehnke wrote: I checked the MQ http://www.mqseries.net/phpBB/viewtopic.php?t=51507&sid=87a0b9bc58377071bd4f1327cd8caecb Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error. Another application using input exclusive? (Though frankly I'd have expected a different reason code for that). Something else accessing the queue? Have you checked the queue or just the application that's supposed to be using the queue?_________________Honesty is the best policy. Insanity is the best defence. Back to top chris boehnke Posted: Mon Nov 09, 2009 12:54 pm Post subject: Re: reason code 2042 PartisanJoined: 25 Jul 2006Posts: 369 Vitor wrote: chris boehnke wrote: I checked the MQ Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error. Another application using input exclusive? (Though frankly I'd have expected a different reason code for that). Something else accessing the queue? Have you checked the queue or just the application that's supposed to be using the queue? I checked with only application and the options are shared. Is there a possibility like application got disconnected accidently and trying to open the same queue again and getting 2042? Back to top Vitor Posted: Mon Nov 09, 2009 1:08 pm Post subject: Re: reason code 2042 Grand High PoobahJoined: 11 Nov 2005Posts: 23698Location: Ohio, USA chris boehnke wrhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://stackoverflow.com/questions/25630602/websphere-mq-error-with-reason-code-2042-on-a-get workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs http://www.tek-tips.com/viewthread.cfm?qid=74343 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 other. Join mq error them; it only takes a minute: Sign up Websphere MQ - error with reason code 2042 on a get up vote 2 down vote favorite We're getting an intermittent error on a ImqQueue::get( ImqMsg &, ImqGetMessageOptions & ); call with reason code 2042, which Should Not Happen™ based on the Websphere documentation; we should only get that reason code mq error code on an open. Would this error indicate that the server could not open a queue on its side, or does it indicate that there's a problem in our client? What is the best way to handle this error? Right now we just log that it occurs, but it's happening a lot. Unfortunately I'm not well-versed in Websphere MQ; I'm kind of picking this up as I go, so I don't have all the terminology correct. Our client is written in C++ linking against libmq 6.0.2.4 and running on SLES-10. I don't know the particulars for the server other than it's running version 7.1. We're requesting an upgrade to bring our side up-to-date. We have multiple instances of the client running concurrently; all are using the same request queue, but each is creating its own dynamic reply queue with MQOO_INPUT_EXCLUSIVE + MQOO_INPUT_FAIL_IF_QUIESCING. c++ websphere-mq suse share|improve this question asked Sep 2 '14 at 19:10 John Bode 59.9k858107 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote If the queue is not
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. IBM: MQSeries Forum at Tek-Tips HomeForumsProgrammersEAI Distributed/Component ProgrammingIBM: MQSeries Forum MQJE001: Completion Code 2, Reason 2042 thread332-74343 Forum Search FAQs Links MVPs MQJE001: Completion Code 2, Reason 2042 MQJE001: Completion Code 2, Reason 2042 sudhya (Programmer) (OP) 18 Apr 01 19:42 Hi I am trying to access a particular QUEUE running on MQSeries v5.1 on NT Server. I am using NT JAVA client on myNT machine to connect to MQSeries server.The sample JAVA APPLICATION (MQSample.java) programrunning on client works fine and is able to access SYSTEM.DEFAULT.QUEUE.I have made small changes in the sample program to access NEWLY created local queue on MQ Server, which also works fine.But the problem is:1. When I tried to access other local queues which are on the same SERVER machine which were createdlong back---I get the following error when I run modified MQSample.java to access old queues.( IMP:Old Queues are functioning)Error is:MQJE001: Completion Code 2, Reason 2042An MQSeries error occurred : Completion code 2 Reason code 2042When I went to through IBM doc , it says that QUEUE is already (MQRC_OBJECT_IN_USE) in use and Enable your queue tobe handled by MORE THAN one application.So how to resolve this problem?Any info on this will certainly helps me.Thanks in advance.Sudhir Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-