| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue in mqrc_global_uow_conflict |
« View previous topic :: View next topic » |
| Author |
Message
|
| HeavyStorm |
 Posted: Fri Oct 28, 2016 1:37 pm Post subject: Issue in mqrc_global_uow_conflict |
 |
|
Newbie
Joined: 28 Oct 2016
Posts: 2
|
Hi! I'm trying to setup a distributed transaction between WMQ and SQL Server through MS DTC but am running on a strange issue.
Intermittently I get a mqrc_global_uow_conflict from MQ. Googling it yields only poor information.
The exception ain't the worse problem, since I'd expect the transaction to be backed out. But right now, I'm getting a strange behavior where a few messages are "stuck" in WMQ. I can't get them, nor can I clean the queue through Explorer. Researching, it seems messages are on a uncommited state, so I can't touch them.
I can send more info about my setup as needed. Thanks a lot for any information. |
|
| Back to top |
|
 |
| hughson |
| Posted: Sun Oct 30, 2016 1:51 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Did you find the MQRC description in Knowledge Center?
| IBM Knowledge Center wrote: |
2351 (092F) (RC2351): MQRC_GLOBAL_UOW_CONFLICT
Explanation: An attempt was made to use inside a global unit of work a connection handle that is participating in another global unit of work. This can occur when an application passes connection handles between objects where the objects are involved in different DTC transactions. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction.
This error does not occur for nontransactional MQI calls.
This reason code occurs only on Windows and z/OS.
Completion Code: MQCC_FAILED
Programmer response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. |
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| hughson |
| Posted: Sun Oct 30, 2016 2:10 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
I assume you are the same person that asked this question over on StackOverflow?
If so, I note from your description that that you say:-
| StackOverflow user: Bruno Brant wrote: |
| I reuse the MQQueueManager object and the MQQueue object in a loop, and thus between transactions. |
From the error explanation posted earlier, note:-
| IBM Knowledge Center wrote: |
This can occur when an application passes connection handles between objects where the objects are involved in different DTC transactions. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction.
If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. |
Could this be your problem?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| HeavyStorm |
| Posted: Mon Oct 31, 2016 9:34 am Post subject: |
|
|
Newbie
Joined: 28 Oct 2016
Posts: 2
|
@Morag,
Thanks for taking the time and interest to responding.
Indeed, that's my post in SO.
I'm not sure that's my problem. The exception is risen intermittently, and I have yet to identify what is causing it.
In any case, my current issue is that whenever the process fails, a few messages are left in an "uncommitted" state in WMQ. Those messages get stuck. |
|
| Back to top |
|
|
| hughson |
| Posted: Mon Oct 31, 2016 1:19 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| HeavyStorm wrote: |
| I'm not sure that's my problem. The exception is risen intermittently, and I have yet to identify what is causing it. |
I'm curious why you don't think that's your problem? Do you have locking to ensure that the connection isn't reused in the loop until the asynchronous processing for the UoW is completed? If so, please share how. 
| HeavyStorm wrote: |
| In any case, my current issue is that whenever the process fails, a few messages are left in an "uncommitted" state in WMQ. Those messages get stuck. |
Have you read up about the dspmqtrn and rsvmqtrn commands?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| 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
|
|
|
|
