| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| PROBELEM in MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqwf |
 Posted: Tue Aug 24, 2004 3:09 am Post subject: PROBELEM in MQ |
 |
|
Acolyte
Joined: 10 Oct 2002
Posts: 62
|
First the program connects to the queue manager
and then it does some work
and after some time it tries to send the message
that time is fails saying 2009 error or sometimes 2019
It also happens that one binary tries to connect to the queuemanager and then send mesages and get messages when it is doing that in between it gets 2009 or 2019 exception
MQSeries server is on 5.2 and client is on 5.3
Can anyone tell me why does this happpen |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 24, 2004 5:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The connect you have made to the queue manager has closed down or been broken somehow. Or the handle you are using is out of scope
You can find a listing of all the Reason codes in the Messages manual.
It will tell you that
| Quote: |
2009 X'07D9' MQRC_CONNECTION_BROKEN
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 WebSphere 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.
Corrective action: 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. |
and
| Quote: |
2019 X'07E3' MQRC_HOBJ_ERROR
The object handle Hobj is not valid. If the handle is a shareable handle, the handle may have been made invalid by another thread issuing the MQCLOSE call using that handle. If the handle is a nonshareable handle, the call may have been issued by a thread that did not create the handle. This reason also occurs if the parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
Corrective action: Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. For MQGET and MQPUT calls, also ensure that the handle represents a queue object. Ensure that the handle is being used within its valid scope. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqwf |
| Posted: Tue Aug 24, 2004 9:21 pm Post subject: Problem In MQ |
|
|
Acolyte
Joined: 10 Oct 2002
Posts: 62
|
I open a connection to Queuemanager and immediately open a queue and try to send a message...still it gives a 2009 or 2019 error.
It also happens that a binary is getting the message and sending the message and while doing this it gives this 2009 and 2019 error suddenly.
And this error is not consistent also...sometimes it takes place or sometimes it doent
Can you help me |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Aug 25, 2004 5:26 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I've seen some flaky 2009 errors when I connect JMS related clients that are at different levels than the qmgr. You didn't say what your client was. You didn mention that your server was at MQ 5.2. You should be able to connect a 5.3 client to it. However, MQ 5.2 is out of support. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 25, 2004 5:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can also get 2009 errors when the maximum number of open channels is reached.
That would explain the intermittent nature.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
