For a multiple number of reasons related to performance in how we use use H2
we create a bunch of h2 DBs. About 18 or so.
Anyways our startup time of the app slowed down and the only way I was able
to get it to work better was FILE_LOCK=NO. I also created multiple threads
to start each DB. With FILE_LOCK=SOCKET this still locked on
"Thread-7" prio=10 tid=0x00002aabbcb27800 nid=0x505f waiting for monitor
entry [0x000000004163e000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.h2.engine.Engine.openSession(Engine.java:140)
- waiting to lock <0x00002aab722505d0> (a org.h2.engine.Engine)
at org.h2.engine.Engine.getSession(Engine.java:125)
at org.h2.engine.Session.createSession(Session.java:122)
at
org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:241)
at org.h2.engine.SessionRemote.createSession(SessionRemote.java:219)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:111)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:95)
The NO FIILE_LOCK fixes this. In our app nothing except our one class access
it. Also it is a cache loader for JBOSS Cache and it implements its own
locking for the most part.
Our LOCKING=0 anyways regarding h2.
Is there anything I am not thinking of?
--
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.
