MQSeries.net :: View topic - Using MQ Connection pooling with a standalone client

psreddy · Posted: Wed Sep 01, 2010 7:50 am Post subject:

Hi,
I have a Stand alone application (Which is not using WebSphere Application server or JMS) which uses Websphere MQ 6.0 for connecting to MQ Queue to post messages to send Queue and receives the messages from receive Queue. This application opens Queue connection every time it try to send message to Queue and closes it once the message is posted.

Now I have to implement MQ connection pooling. I did searched the IBM site and found the following API for connection pool implementation.

MQSimpleConnectionManager myConnMan = new MQSimpleConnectionManager();
myConnMan.setActive(MQSimpleConnectionManager.MODE_ACTIVE);
myConnMan.setTimeout(3600000);//millisecs
myConnMan.setMaxConnections(33);
myConnMan.setMaxUnusedConnections(50);
myConnMan.setActive(MQSimpleConnectionManager.MODE_INACTIVE);

And I get the queue manager as follows
MQQueueManager qMgr = new MQQueueManager(getMQQueueManagerName(), mqEnv, myConnMan);
queue = qMgr.accessQueue(getMQQueueName(),qOpenOptions, null, null, null);

I tried to use this API in my stand alone application. But I see there is no improvement in connection creation. i.e I see the same number of connections are created even after the above implementation.

My application can create 10 threads and process the simultaneous requests.

My questions are:
1. Can we implement the MQ connection pooling with stand alone applications using the above MQ API?
2. If not, do we need to implement a separate layer for managing the MQ connection pooling?.

Could experts please shedd some light... Its urgent Please..

Thanks in Advance
psreddy