Hi Diego,
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?
If you use persistent connections with DBCP then you can just use a
SimpleConnectionManager since there will be a 1-to-1 mapping between
your application-controller and controller-database connections.
If you are not using persistent connections (which is the default), DBCP
only keeps a pool of connections with the controllers but the
controllers actually don't allocate any connection with the databases
(they just do that on-demand when you issue queries). In that case, you
want to have both connection pools.
If your database driver does transparent connection pooling (the driver
is smart enough to pool connections for you), then you don't need a
connection pool. This is the case of the Sequoia driver, so using DBCP
is optional on top of Sequoia.
Thanks for your interest in Sequoia,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[EMAIL PROTECTED]
https://forge.continuent.org/mailman/listinfo/sequoia
