Connection pool or singleton


#1

I am using a java compute node in websphere message broker.

Each message flowing through the broker gets a new thread. The java compute node executes in its own thread and cannot share anything outside that thread. Even JDBC must go through a configurable service to get a connection to the database.

So if I create the client and connect to the server and don’t do client.shutdown() I get a too many files open error in Linux. If I do client.shutdown() my performance goes away.

any ideas on a solution?


#2

Hello,

The singleton is the way to go with Couchbase Java SDK.
I am not familiar with IBM Message Broker, any way to have single instance somehow?

Tug