H2 database consule lockings

[moshi cochem]

Hi, I developed a java application, I can test it using the eclipse.
That application is working well with H2 DB , using it and releasing it.
I made a jar out of it, and I use it in a web application, running on tomcat.
The apache tomcat is locking my db.
When I run my application in java simple application, the db is released,
but when I run it on tomcat , the db is locked.
Why ?
Before returning the final answer from the jar, I do:

if(conn!=null)
if(!conn.isClosed())
conn.close();

Thanks

[Salil Vverma]

Hi moshi,

I am curious to know why are you using H2 database rather than using mysql,which is most widely used open source database. In mysql you would not face the issue of database locking.

You can download mysql freely from the following url

[moshi cochem]

Does anyone have an idea ?
thanks

[Ulf Dittmer]

How does the web app use H2 - as a standalone server or in embedded mode? If it's embedded, then no other process can access it.

[moshi cochem]

Hi,
But I close the connection, it is not enough ?

[Ulf Dittmer]

Not if you're using embedded mode. For HSQLDB, the "Closing the Database" section of the documentation would be relevant; I'm sure H2 has something similar.

[moshi cochem]

I solve it by writing in the connection: FILE_LOCK=NO
Thanks.

[Ulf Dittmer]

You have read the documentation for that feature at http://www.h2database.com/html/features.html#database_file_locking, and you do understand the potentially very bad consequences, right?