| Author |
Message
|
| ljurkovic |
 Posted: Mon Oct 16, 2006 8:46 am Post subject: MQ ETC client hangs when run under a DTC transaction when |
 |
|
Newbie
Joined: 10 Oct 2006
Posts: 4
|
I have a ServicedComponent that gets or puts a message to a queue along with some database update that needs to run as one transaction. Everything works fine when the queue manager is up and runing, but if it's down the porgram hangs when trying to open the queue manager. No exception is thrown.
When the same code is run in a non-transactional environment then a correct exception with reason code 2059 is thrown. The same behavior is experienced in both .Net 1.1 and 2.0. The language used is C# and here is the code that access the queue:
Hashtable connectionProperties = new Hashtable();
connectionProperties.Add(MQC.HOST_NAME_PROPERTY, managerHostName);
connectionProperties.Add(MQC.PORT_PROPERTY, int.Parse(managerPort));
connectionProperties.Add(MQC.CHANNEL_PROPERTY, managerChannelName);
MQQueueManager queueManager = new MQQueueManager(managerName, connectionProperties);
Has anybody experienced this behaviour? Is there any other property I could specify in the MQQueueManager constructor I don't know about?
Thanks,
Ljubo |
|
| Back to top |
|
 |
| tleichen |
| Posted: Mon Oct 16, 2006 11:27 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
It sounds like the transactional piece is waiting for a response from the queue manager and is not completing the unit of work until it gets one. Sounds like a possible coding problem with the transaction. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| ljurkovic |
| Posted: Tue Oct 17, 2006 5:21 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2006
Posts: 4
|
| The thing is that this happens only if the queue manager is unavailable and in that case the client should throw an exception. If the queue manager is up and runing then everything works fine. It just looks to me like the client gets confused about the transaction context it was runing under. |
|
| Back to top |
|
|
| tleichen |
| Posted: Tue Oct 17, 2006 9:10 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
What platforms are we talking about here?
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 17, 2006 9:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| tleichen wrote: |
| What platforms are we talking about here? |
C# and .NET and DTC only run on, umm... one... platform, really.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tleichen |
| Posted: Tue Oct 17, 2006 5:36 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Oops! That's what I get for looking at four different posts at once! 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| ljurkovic |
| Posted: Fri Oct 20, 2006 4:45 am Post subject: MQ ETC client hangs (Solved) |
|
|
Newbie
Joined: 10 Oct 2006
Posts: 4
|
It's very hard to find support articles for .Net specific problems, but apparently this was a known issue with MQ v6.0.0.0 Windows client. This problem is described by APAR IC48309:
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg1IC48309
I needed the fix pack 6.0.1.1 and that got me back in business.
Just in case somebody else runs into the same wall, there you have it.
Cheers,
Ljubo |
|
| Back to top |
|
|
|
|
