I run a web app in embedded mode. I keep a single connection open as a
"control" connection. Then when the app closes I close that connection.
On the last connection closing the database closes. Seems to work
well.... I also use that control connection while the application is
running for some maintenance things to take the database online and
offline (and block any new connections opening it up while I am doing
those things).
Wildam Martin wrote:
On Wed, Feb 17, 2010 at 22:01, rmuller <[email protected]> wrote:
@Kerry:
I close all connections before shutting down the app. So as far as I
understand it this is no problem.
But you are talking about a webapp - hence multiple threads possible...
The files are created on the server (normal webapp) using h2 in
embedded mode.
... I am not sure about the capabilities of H2 in such an environment,
but I would not use the embedded mode in such a case because of
application life cycle would seem to me too unsure. - But this is just
my gut feeling.
--
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.
