BoneCP和Netty基础

Question

In order to efficiently use connection pooling via BoneCP while programming a Netty server- where is the correct place for the connection pool and where to get a new connection for that pool?

At a glance- I'm thinking that BoneCP should be some sort of global/singleton initialized just once in the main server, and then each handler (ie the class passed as "handler" to the pipeline) references that singleton to grab a new connection... but I don't see any examples of that on the net and, being new to Java, I'm a little concerned to jump right in with that approach. Would be great to hear an experienced voice!

Answer 1

Yes, a channel handler can very well use the BoneCP connection pool, but you should definitively insert an ExecutionHandler in front of the BoneCP handler. You do not want to issue blocking db calls in a netty IO worker thread.

Answer 2

There's also this defined in bonecp:

public ListenableFuture getAsyncConnection(){

    return this.asyncExecutor.submit(new Callable<Connection>() {

        public Connection call() throws Exception {
            return getConnection();
        }});
}