[Building Sakai] Does minIdle at javax.sql.BaseDataSource stil work?

[Matthew Jones]

dbcp hasn't been upgraded since 1.2.2 in (SAK-9578) in 2.5. We haven't moved
to 1.4/1.3 as it required a commitment to switching to JVM 1.6 and
significant testing. At Michigan we were planning on investigating this as
there have been plenty of fixes since 2007 and have had random issues
related to pool exhaustion that may have been fixed. We needed to wait until
rolling to 2.7 and 1.6 JVM, which was done last week.

I'm not sure about commons-pool getting upgraded or not.

You could try changing some of the other properties to see if that gets you
back to your expected behavior such as "timeBetweenEvictionRunsMillis@".

https://source.sakaiproject.org/svn/kernel/trunk/kernel-component/src/main/webapp/WEB-INF/db-components.xml

-Matthew

On Sun, Jan 2, 2011 at 6:40 PM, Kenwrick Chan <kchan at hawaii.edu> wrote:

> Folks,
> We've just upgraded from sakai 2.5.x to sakai 2.7.1.  With 2.5.x if you
> wanted to have 225 database connection you'd put the following in
> sakai.properties.
>
> minIdle at javax.sql.BaseDataSource=0
> maxIdle at javax.sql.BaseDataSource=225
> initialSize at javax.sql.BaseDataSource=225
> maxActive at javax.sql.BaseDataSource=225
>
> This same settings doesn't appear to work with 2.7.1.  It starts out fine,
> but over time drops down significantly [which is very obvious now during the
> holiday break].  This is with mysq
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110103/c2956d2d/attachment.html