Hi,
I'm trying to establish how exactly to configure connection pooling with
Sequoia.
Without sequoia, I'm using Apache DBCP to pool connections to Apache Derby,
and all works fine.
Now with sequoia, as I understand it, there are two sets of connections to
consider:
i) from my app to the controller
ii) from the controller to the backends (derby).
So my questions are:
1) when you specify connectionpooling=true on a sequoia jdbc url, I assume this
is for pooling from the app to the controller.
2) If so, I'd prefer to continue to use DBCP, for consistency in sequoia vs
non-sequoia environments - should using DBCP & connectionpooling=false work ok?
3) for the connections between the controller & backend, is this controlled
purely via the ConnectionManager setting in the virtual database config (e.g.
using a VariablePoolConnectionManager)? I gather from other posts, the
recommended config is to have a minPoolSize of 0 and a high value for
maxPoolSize - presumably at least as large as the number of connections from
app to controller?
many thanks for any advice,
Andrew Lawrenson
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
