Connection Pooling should work in multi threaded environments with transactions.
I think the current design may be flawed. I think there should be a special connectionpool with which connections can be linked. in a multi-threaded environment, you want the thread to grab a connection, use it, and release it. at the moment, if you want to start a transaction, with connection pooling enabled, the current connection is basically blocked as it does not do anything smart in tracking the underlying connection to a thread. I currenltly get an error - cannot start transaction when one is already active... so I have to go an create another connection to workaround, which doesn't seem right cause the pooling options are not shared in anyway? I'm reverting to creating my own threadpool which is not ideal.