Didi, You said that the COM+ interface gives session pooling.
I accept that it provides an MQSession object that's shared between threads, and that you can create MQQueueManager objects or use the AccessQueueManager() method to get a QM object. However I can't see anything in the docs that suggest that it does session pooling whereby when an MQQueueManager object is destroyed ( or a .Disconnect() is issued) that an MQDISC is NOT actually issued (at least for a while - say 30 mins) and if a new MQQueueManager object is created for that thread the connection is re-used. To me the docs just suggest a light wrapping of the MQI. Or does the MQSession.AccessQueueManager() method behave differently from explicitly constructing an MQQueueManager, setting the Name Property and issuing a Connect(). Please could you clarify this for me? Thanks Dave Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
