|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
2009 MQ Exception B |
« View previous topic :: View next topic » |
Author |
Message
|
bhr |
Posted: Tue Feb 18, 2003 9:34 pm Post subject: 2009 MQ Exception B |
|
|
Newbie
Joined: 18 Feb 2003 Posts: 1
|
Hello Everyone,
I have a couple of questions around the 2009 (Broken Connection) MQ Exception
1. Under what conditions this exception would occur?
2. Is there a workaround for the problem?
Details of the project
1. Programming langauge - JAVA 1.4
2. O/S - Unix :Sun Solaris
3. MQ version: 5.2
We are facing this nagging issue and unable to find a convincing solution. Any help would be appreciated.
Thanks in advance. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Feb 19, 2003 4:47 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
This is what the manual states:
Quote: |
MQRC_CONNECTION_BROKEN (2009)
Explanation: Connection to the queue manager has been lost. This can occur because the queue manager has ended. If the call is an MQGET call with the MQGMO_WAIT option, the wait has been canceled. All connection and object handles are now invalid.
For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED.
Completion Code: MQCC_FAILED
Programmer Response: Applications can attempt to reconnect to the queue manager by issuing the MQCONN or MQCONNX call. It may be necessary to poll until a successful response is received.
On z/OS for CICS applications, it is not necessary to issue the MQCONN or MQCONNX call, because CICS applications are connected automatically.
Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.
|
I think this answers both your questions. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
bower5932 |
Posted: Thu Feb 20, 2003 7:00 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
There have been quite a few fixes in the 2009 area. If you are running with MQ 5.2 without any CSDs, I'd suggest getting the latest CSD. It might help you out. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|