Thomas, Thanks for the answer. It would be helpful to shutdown the entire server (tcp & pg together) without using 'kill'. I think at minimum providing a '-pgShutdown' to stop the pgServer would be immediately helpful. On this same thought, I also don't know the side-effects of starting them separate. Does running two separate servers (1 as tcp and the other as pg in different Java processes) have any impact on locking or lead to possible data corruption when accessing the same database? I'm guessing it does.
Also, have you considered setting up a Wiki Doc so user's can contribute how-to's ? I'd be happy to contribute. I think JamWiki works with H2. Cheers, Chris On Dec 9, 12:17 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > Currently you need to kill the Java process, unless you use some > tricks (for example stop the process using JMX or so). > > I guess it would make sense if -tcpShutdown would also stop the > pgServer (and webServer) listeners if those were started at the same > time, using > > java ... -tcp -pg > > I will implement this (not sure if for the next release already). What > do you think? > > Regards, > Thomas -- 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.
