On 2012-03-27 00:06, steve.ebersole wrote:
Note that this is NOT using H2 JTA/XA support. It is simply using H2
connections obtained via DriverManager wrapped in an Enhydra
DataSource. The url is 'jdbc:h2:mem:db1;DB_CLOSE_DELAY=-1;MVCC=TRUE'.
Anyone see anything obvious? If it weren't for the
'DB_CLOSE_DELAY=-1', I would think the problem was the data cache
being dropped across the multiple connections. That or somehow the
commit call on the connection is not being handled properly.
Do you realise your URL says to __negative__ one seconds for the close
delay?
That means that the moment that the last connection closes, the DB will
be destroyed.
I think you should be using __positive__ one seconds, and I've added
some code to the next version of H2 to catch such mistakes i.e.
DB_CLOSE_DELAY must be >= 0
--
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.
