C++ Connection pool
MQ Java support the concept of a connection pool, but there doesn't seem to be a similar piece in the C++ API. Anyone been there and done that? Regards, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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
Re: C++ Connection pool
Hi Dave, On what platform do you wish to do it? Using COM+ gives you pooling for C++ on windows, as for other platforms, we needed to write code, but that was a long time ago... Cheers Didi - Original Message - From: "David C. Partridge" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 25, 2004 6:21 PM Subject: C++ Connection pool > MQ Java support the concept of a connection pool, but there doesn't seem to > be a similar piece in the C++ API. > > Anyone been there and done that? > > Regards, > David C. Partridge > Technical Products Director > Primeur Security Services > Tel: +44 (0)1926 511058 > Mobile: +44 (0)7713 880197 > > 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 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
Re: C++ Connection pool
Hi there Didi - long time no speak. I don't know - the question was asked on behalf of a development company working for one of our customers, and I don't know the platform they are using. Most likely is Unix or Windows David 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
Re: C++ Connection pool
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
Re: C++ Connection pool
Hi Dave, Indeed long time no speak, to much work to little time as usual, I cannot say I found a reference about connection pooling in COM+ but I can tell you it is very much empirically so. We noticed the SVRCONN take a while to close and do not correlate with the number of application instances we have up and running! When the MTS support pack was available I do think I read something along those lines but I am not sure, when I will have some time I will check it out, meanwhile here we assume it is so, because we issue connects and disconnects as much as we need and it does not hinder performance. Hopefully I was clear, if not feel free to give me a call, Cheers Didi - Original Message - From: "David C. Partridge" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 26, 2004 12:31 PM Subject: Re: C++ Connection pool > 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 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
