search

google-code-export / h2database

Automatically exported from code.google.com/p/h2database
0 stars 1 forks source link

Deadlock in Pooling mechanism? #250

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
I've seen this multiple times now.  I will try to come up with a definitive 
test case.  I'm not even sure its in the Pooling mechanism.

connection string: MODE=MYSQL;AUTO_SERVER=true
Using built-in pooling.

The last time it locked up I sent the H2 Console a partial command like "SHOW". 
 The Console never responded and my Webapp stopped processing connection 
requests.

What is the expected output? What do you see instead?
Connections sometimes block and subsequent getConnection fails with JDBC login 
timeout.

What version of the product are you using? On what operating system, file
system, and virtual machine?

1.2.144

Do you know a workaround?

Maybe.  Use Apache Pool (which I use for MySQL so it was easy enough to 
reconfigure).

How important/urgent is the problem for you?

Not urgent for me.  I have Apache Pool - unless the failure happens with that 
too suggesting its not the H2 Pool at all.

In your view, is this a defect or a feature request?

Defect, but I can't pinpoint the failure point.

Original issue reported on code.google.com by James.Mo...@gmail.com on 2 Nov 2010 at 7:03

GoogleCodeExporter commented 9 years ago 
If you get problem again, please post a few full thread dumps. You can get 
those using jps -l / jstack <pid>, or kill -QUIT <pid>. After that, please add 
a comment here and I will reopen the issue.

Original comment by thomas.t...@gmail.com on 5 Nov 2010 at 11:46