We were using c3p0 v0.8.5.2 with Oracle Thick driver in
a project using Oracle database. We were noticing
growth in the Java VM size, which eventually used to
exceed 2GB limit imposed on processes running in a 32
bit OS and crash soon thereafter. After several months
of investigation, we finally tracked the growth in
memory down to the fore-mentioned version of the c3p0.
The problem disappeared after downgrading to v0.8.5
downloaded from this web-site. So looks this version
had a bad memory leak. We are also noticing the leak
and the growth in size also in later versions
including v0.9.x. I think this should be looked up
carefully as other users may face the same problem.
Are c3p0 parameters were:
Log in to post a comment.