Thanks Everyone for the answers. Peter, I know about the AUTO_SERVER feature, it's just a different thing from what I want to have. AUTO_SERVER means that the first process accessing the database does it as embedded while keeping a tpc listener for subsequent connections.
Now imagine this scenario. Process1: access the database and becomes the holder of the lock. Process2: access the database and it finds it loked, so connects to Process1 with tcp connection. Process1: ends its task. Process2: has a broken connection now. What I want is to make sure that the Process2, in my case a web application that will be always up, is always the one who holds the lock. And this is how it is specified by this page: "Using a Servlet Listener to Start and Stop a Database" http://www.h2database.com/html/tutorial.html#web_applications And I think there may be a but in the configuration exposed in the documentation. I just discovered H2, and I think it's the best. I am migrating my app from a "nosql" store to H2. H2 it's just awesome; I'm looking at the source code, and it is quite incredible, sort of alien technology! :-) Thanks for the help. Luigi. -- 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.
