Hi Andrew,
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.
Yes.
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?
Yes.
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?
This is correct. maxPoolSize can also be set to 0 (no limit) but it
should never exceed the maximum number of connections accepted by the
database.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
