I am not sure what you mean. I always call connection.close() so that the connections will go back to the pool. The pool (which is of Tomcat) decides when to actually close the connections. So as far as your comment that the connection pool is not disposed, there is an analysis on this on the Tomcat dev group thread I posted here. Did you get a chance to read that thread? Also I have send you a sample code. Did you tried that?
On Apr 25, 9:52 am, Thomas Mueller <[email protected]> wrote: > Hi, > > I didn't have time to look at it yet. > > I believe the problem is that the database connections are not closed, > probably because the connection pool is not disposed. So I believe it's an > application problem, and not a problem within H2. > > Regards, > Thomas > > > > > > > > On Tuesday, April 24, 2012, Jim wrote: > > Hi, > > Did you have a chance to look into this? Is this indeed an H2 problem > > as stated by Tomcat dev? > > > On Apr 10, 10:01 pm, Thomas Mueller > > <[email protected]<javascript:;> > > > wrote: > > > Hi, > > > > I would like to understand what the problem is, but could you provide > > > the configuration you are using, and if possible a simple test case > > > please? That would help a lot. > > > > Regards, > > > Thomas > > > -- > > You received this message because you are subscribed to the Google Groups > > "H2 Database" group. > > To post to this group, send email to > > [email protected]<javascript:;> > > . > > To unsubscribe from this group, send email to > > [email protected] <javascript:;>. > > For more options, visit this group at > >http://groups.google.com/group/h2-database?hl=en. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
