| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_UOW_ENLISTMENT_ERROR on non-transactional MQ client |
« View previous topic :: View next topic » |
| Author |
Message
|
| JohnGee |
 Posted: Tue Jul 12, 2005 7:55 am Post subject: MQRC_UOW_ENLISTMENT_ERROR on non-transactional MQ client |
 |
|
Newbie
Joined: 07 Apr 2005
Posts: 8
|
| Could not find a problem with my particular facts. We have a client (CSD09) installed on a Windows 2003 SP1 server. I think the client is getting confused and trying to enlist in a distributed transaction, which there is one, when all we really want is MQ work to be done within its own local MQ transaction. I can run a client app that doesn't have a distributed transaction running and the MQ transaction works. Am I reading the problem right and what can I do to make sure the MQ client won't try to enlist in a distributed transaction? Thanks! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 12, 2005 10:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the client application is written to participate in a two-phase transaction, then you can not run it on a regular MQ Client.
So if it is incorrectly trying to participate in a two-phase transaction, then you need to change the application.
If it is correctly trying to participate, then you need to change where it is running - put it either on a server or a machine with the Extended Transactional Client.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 12, 2005 1:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is your programming environment ?  |
|
| Back to top |
|
|
| JohnGee |
| Posted: Tue Jul 12, 2005 2:00 pm Post subject: |
|
|
Newbie
Joined: 07 Apr 2005
Posts: 8
|
| VB6. We created a COM+ entry for the application dll on the client PC and disabled transactions for it. This eliminated the problem. As it turns out that is the way the COM+ entry was defined on the server... so that is likely why we didn't encounter the problem on the server. Thanks for the responses. |
|
| 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
|
|
|
|
