search

google-code-export / h2database

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

receiving Connection is broken: "session closed" [90067-134] in concurrent batch update #202

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Before submitting a bug, please check the FAQ:
http://www.h2database.com/html/faq.html

What steps will reproduce the problem?
(simple SQL scripts or simple standalone applications are preferred)
1. The database is on a remote server, running in server mode, accessed via TCP
2. The client is a multithreaded application (or servlet) that is
concurrently doing batch updates using hibernate3 and dbcp (or c3p0) data
source.
3. client threads occasionally getting "Connection is broken: "session
closed" [90067-134]" from h2 DB

What is the expected output? What do you see instead?
Expected: not to receive the error.
Instead: error is received with version 134 and goes away with 128, it was
actually observer first after upgrade from 128 to 134

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

Do you know a workaround?
revert back to version 128

How important/urgent is the problem for you?
medium to high, we upgraded to 134 because it fixed a different issue.

In your view, is this a defect or a feature request?
defect, it didn't exist in version 128

Please provide any additional information below.

Original issue reported on code.google.com by hahme...@gmail.com on 20 May 2010 at 10:51

GoogleCodeExporter commented 9 years ago 
Hi,

What is your database URL? Could you append ;TRACE_LEVEL_FILE=3 to the database 
URL,
re-try, and then upload the .trace.db file(s) (there should be on on the server 
side
and another on the client side; you may need to search for the client file in 
the
current working folder of the client application)? Please compress the files 
before
uploading.

Regards,
Thomas

Original comment by thomas.t...@gmail.com on 24 May 2010 at 8:08

GoogleCodeExporter commented 9 years ago 
I'm afraid I will have to close this bug.

Original comment by thomas.t...@gmail.com on 7 Jun 2010 at 4:26

GoogleCodeExporter commented 9 years ago 
It looks like the error message is wrong. I could reproduce the error in the 
following way: try to connect to a server when the server is not running.

I will change the error message.

If this is not the problem, please add a comment - I will re-open this issue.

Original comment by thomas.t...@gmail.com on 28 Jun 2010 at 6:48