Hi, It looks like you are using a connection pool, so that physical JDBC connections should be re-used. But in the stack trace, there are a lot of physical JDBC connections created. The only explanations I have is that either the connection pool doesn't work as it should (that's unlikely), your application is opening connections without closing them, or the pool size is too small.
Regards, Thomas On Wed, Nov 28, 2012 at 7:30 AM, Noel Grandin <[email protected]> wrote: > I don't see any signs of a deadlock there, the key threads are all > runnable. > > Judging by the number of pending connections, however, you may have a > performance problem. > > > On 2012-11-28 01:25, Larry Ruiz wrote: > >> I have a deadlock after upgrading from 1.2.138 to 1.3.169, the database >> is embedded >> > > -- > 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 h2-database+unsubscribe@** > googlegroups.com <h2-database%[email protected]>. > For more options, visit this group at http://groups.google.com/** > group/h2-database?hl=en <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.
