On Wed, Sep 05, 2007 at 04:26:34PM -0400, Lance Speelmon wrote:
> The first sign of trouble came from the fact that DBCP was having
> trouble obtaining and maintaining connections to Oracle. DBCP has a
> nasty bug that can be triggered in these kinds of conditions that
> results in a deadlock situation. To resolve the DBCP bugs, we
> switched to the c3p0 connection pool. C3p0 behaves much more stably
> and predictably under heavy load and can recover better from
> connection issues with Oracle. This is a drop-in replacement for
> DBCP and I am going to recommend that Sakai switch to this connection
> pool as a default in the 2.5 release.
what were the dbcp parameters you were using per appserver and what are they
under c3p0?
Any reason why did increasing the connection pool so drastically helped?
Thanks,
Adi
----------------------
This automatic notification message was sent by Sakai Collab (
https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.
