| Author |
Message
|
| dakoroni |
 Posted: Tue Apr 28, 2020 5:07 am Post subject: MQ client 8.0.0.8 - Distributed transaction issues - Upgrade |
 |
|
Acolyte
Joined: 10 Jan 2020
Posts: 50
|
Hello MQ inst/support forum users,
I have a bank customer using MQ client 8.0.0.8 for .NET (v4.6.01590) based apps as well as several "tighted" bank services and flows (i.e. SwiftLiveService, DCTHealthMonitor, etc) and reported distributed transaction issues (I have no more details but i can find more info if needed).
There are apps creating many small transactions, other apps monitoring queues all the time and other apps having disitrbuted transactions such as: sql -> sql -> queue.
Customer considers that MQ client 8.0.0.8 doesn't subscribe to msdtc and ignores it..
The question is whether by upgrading to MQ client 8.0.0.14 the distributed transaction problems will be eliminated..
Pls notice that MQ build EoS defined at April 30th, 2020..
I assume the utlimate goal would be to upgrade MQ client to v9.1.x, but I am wondering which might be the limitations or implications to the apps (i.e. .NET upgrade)..
Any advise will be appreciated
Cheers Nick. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Apr 28, 2020 12:38 pm Post subject: Re: MQ client 8.0.0.8 - Distributed transaction issues - Upg |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| dakoroni wrote: |
| ...I assume the utlimate goal would be to upgrade MQ client to v9.1.x... |
Correct...
| dakoroni wrote: |
| ...but I am wondering which might be the limitations or implications to the apps (i.e. .NET upgrade)... |
Only the one the KC may mention, and what your testing of the application may reveal when recompiled using the newer libraries.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| dakoroni |
| Posted: Wed Apr 29, 2020 12:21 am Post subject: Re: MQ client 8.0.0.8 - Distributed transaction issues - Upg |
|
|
Acolyte
Joined: 10 Jan 2020
Posts: 50
|
| Quote: |
Only the one the KC may mention, and what your testing of the application may reveal when recompiled using the newer libraries. |
Since several apps are involved, developers should be engaged in order to outline the problem precisely.
Cust. is not able to provide an accurate problem description (symptoms, errors, etc) for the moment, so I assume we can close this thread for now.
Thanks for yout time and response. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 29, 2020 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
It is not the client by itself that needs to subscribe to the msdtc.
It is the .net code that must use the msdtc
| Code: |
| using System.transactions |
or whatever the correct way to do this in .NET is...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dakoroni |
| Posted: Wed Apr 29, 2020 5:56 am Post subject: |
|
|
Acolyte
Joined: 10 Jan 2020
Posts: 50
|
| fjb_saper wrote: |
It is not the client by itself that needs to subscribe to the msdtc.
It is the .net code that must use the msdtc
| Code: |
| using System.transactions |
or whatever the correct way to do this in .NET is... |
Thanks for the important clarification. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 29, 2020 10:51 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| dakoroni wrote: |
| fjb_saper wrote: |
It is not the client by itself that needs to subscribe to the msdtc.
It is the .net code that must use the msdtc
| Code: |
| using System.transactions |
or whatever the correct way to do this in .NET is... |
Thanks for the important clarification. |
And don't forget to set up MSDTC for XA transactions on the MQ Server box. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
