there is no pooling of MQQueueManager objects within the dotnet implementation. however, writing a simple object pooling solution, if truly needed, is a rather simple task.
things to consider...
1. for a single MQQueueManager instance, all access is synchronized.
2. if one or more of your application's threads requires concurrent access to a queue manager, each thread must create/use its own MQQueueManager instance.
and i'm not too certain i'd do this in the vast majority of cases, but you can disable synchronization within MQQueueManager using one or two different options that i'm not able to remember off the top of the ol' noggin.
if you haven't already, consider reading the "Websphere MQ - Using .NET" redbook. it covers some of this stuff.
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