Hi. There's a thing I don't understand about the Connection Managers used to connect to the backends and how they interact with connection pooling used at application level to connect to Sequoia. The docs say this about SimpleConnectionManager: "basic connection manager that opens a new connection on each request and closes it at the end. It is useful if the underlying driver already implements connection pooling for example."

The thing is... I've got connection pooling implemented in my application (which access the database through Sequoia) using DBCP, is SimpleConnectionManager what I need? Or should I remove the DBCP connection pool from my application config and use a VariablePoolConnectionManager instead? Or should I keep both connection pools?

Thanks in advance.

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to