Thanks for those that have read this article. Finally tracked down on the issue, the connection manager is called inside a transaction scope and as wmq is down, it can not roll back on the transaction ...
I have come across an issue with MQ in .Net where the call to new MQQueueManager() hangs indefinitely if the queue manager is down. No exceptions are thrown, and the call never returns.
I am a newbie to WMQ technology but has to investigate a solution for a client utilizing WMQ in a WAN environment. I have read up on some documentation but am still unclear about a number of as ...