| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQPUT ERROR 2219- PLEASE HELP ASAP |
« View previous topic :: View next topic » |
| Author |
Message
|
| madhu.jakkidi |
 Posted: Wed Jul 02, 2008 4:18 pm Post subject: MQPUT ERROR 2219- PLEASE HELP ASAP |
 |
|
Newbie
Joined: 02 Jul 2008
Posts: 1
|
I am using two threads, its C++/LINUX based application.
Main thread - I loop with MQGET with wait time, say 30 sec.
Thread second - for the message I got in MAIN thread , I put it to different MQ, but same QMGR.
All, MQCONNX(2) and MQOPENs are succussful. BUT when I try to put a message, I am getting 2219 error. No matter, what I use, SHARE_BLOCK option or SHARE_NO_BLOCK option, every thing is good except MQPUT.
If I use only one q mgr handle ,one MQCONNX, still the same problem.
I must be missing something, PLEASE HELP ON THIS. |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Wed Jul 02, 2008 7:44 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 02, 2008 7:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
2219 (X'08AB')
MQRC_CALL_IN_PROGRESS
Explanation:
The application issued an MQI call whilst another MQI call was already being processed for that connection. Only one call per application connection can be processed at a time.
Concurrent calls can arise when an application uses multiple threads, or when an exit is invoked as part of the processing of an MQI call. For example, a data-conversion exit invoked as part of the processing of the MQGET call may try to issue an MQI call.
* On z/OS, concurrent calls can arise only with batch or IMS applications; an example is when a subtask ends while an MQI call is in progress (for example, an MQGET that is waiting), and there is an end-of-task exit routine that issues another MQI call.
* On OS/2 and Windows, concurrent calls can also arise if an MQI call is issued in response to a user message while another MQI call is in progress.
* If the application is using multiple threads with shared handles, MQRC_CALL_IN_PROGRESS occurs when the handle specified on the call is already in use by another thread and MQCNO_HANDLE_SHARE_NO_BLOCK was specified on the MQCONNX call.
Completion Code:
MQCC_FAILED
Programmer Response:
Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit.
* On z/OS, if you want to provide a subtask to allow an application that is waiting for a message to arrive to be canceled, wait for the message by using MQGET with MQGMO_SET_SIGNAL, rather than MQGMO_WAIT. |
Looks like you have a problem with the way you handle your threading 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
