On Tue, Feb 8, 2011 at 10:04 AM, Michael Dick <[email protected]>wrote:
> On Tue, Feb 8, 2011 at 9:49 AM, Joel Halbert <[email protected]>wrote: > >> Hi Mike, >> >> I'm using the defaults, and setting 'partitionCount=3' >> > > Shouldn't matter, but it might help us to reproduce the problem. > > >> Is it possible that the connection is doing any caching of it's own? >> There's no mention of this and it would seem to be beyond the remit of >> it's function. >> > > My guess is that the connection is never closed and has some internal cache > for this row. That combined with BoneCP keeping the same connection 'alive' > is causing the problem. Highly speculative at this point though. > > >> I've decided to use C3P0 for pooling now. Is there any reason to prefer >> DHCP given that it is the out of the box default with OpenJPA? >> > > I have very limited experience with C3P0. It should work, but I don't know > any benefits/cons. > > What about the inverse question: Is there a reason you don't want to use > DBCP? > Just noticed your email to the list from yesterday. Haven't had a chance to look in depth though. Here's the link for other readers : http://openjpa.208410.n2.nabble.com/Issues-with-dhcp-connection-pooling-td5998390.html <snip>
