pooling

We are working on an IBM WebSphere MQ application, and we use JMS API to operate the message. But we have a problem that the connection takes too much time, and we want to pool the JMS connection, for it's a standalone application, we have no application container to provide JNDI or pooling service. So is there a solution to resolve this? For JDBC we can use DBCP or c3p0 to archive pooling datasource, in JMS, is there any similar project that can pool JMS connections? It used to be that the JMS MQConnectionFactory had pooling built in, but it seems that in version 7, it has been removed. Set

i've read a lot of posts regarding problems with auto reconnecting to mysql from hibernate session. Others mention an increase of mysql wait_timeout (not my favorite), using autoReconnect=true (not recommended), testing connection e.t.c. I am currently trying a few options but i would like to ask if anyone has a rock solid solution using tomcat's connection pooling (not hibernate's c3po). I am looking at the most bullet proof jndi settings even if they are not the best performance tuned. Thank you very much, Regards Usman Mutawakil Excellent question. I use to struggle with this question. The

How can I create a pool of connections using HttpClient? I have to make frequent connections to the same server. Is it worth creating such a pool? Is it possible to keep live connections and use it for various requests, and if yes how can I do so? I am developing in Java, using Apache HTTP Client . Tom Anderson [assuming Java, and Apache's HttpClient] Use a ThreadSafeClientConnManager . Pass a single global instance to the constructor of every HttpClient instance. I don't think there's any point in pooling the HttpClients themselves. pssh PoolingClientConnectionManager is Deprecated now . from

Stateless beans in Java do not keep their state between two calls from the client. So in a nutshell we might consider them as objects with business methods. Each method takes parameters and return results. When the method is invoked some local variables are being created in execution stack. When the method returns the locals are removed from the stack and if some temporary objects were allocated they are garbage collected anyway. From my perspective that doesn’t differ from calling method of the same single instance by separate threads. So why cannot a container use one instance of a bean

Does anyone have a good resource on implementing a shared object pool strategy for a limited resource in vein of Sql connection pooling? (ie would be implemented fully that it is thread safe). To follow up in regards to @Aaronaught request for clarification the pool usage would be for load balancing requests to an external service. To put it in a scenario that would probably be easier to immediately understand as opposed to my direct situtation. I have a session object that functions similarly to the ISession object from NHibernate. That each unique session manages it's connection to the