Hi,
> Our client apps and the H2 server are often stopped abruptly when they
> aren't responding
To find out what is happening, please run
jps -l (to get the process id)
jstack -l <pid> (to get a full thread dump)
> -- Is this due to the lobs cleanup at closing you mentioned in some
> earlier posts on this forum?
I don't know, you would see that in the full thread dump
> -- Is there a way to monitor H2 Server activity? like what its doing
> at startup that is taking so long?
See above. Usually a few full thread dumps will show where the problem
is. If you don't understand them, just post them here.
> -- Or is it simply spinning its wheels because the database is broken
> beyond repair?
Usually it's recovery running, but who knows.
> We do use the -tcpShutdown but it doesn't seem to shutdown the server
> as quickly as needed. Our apps only use tcp connections to the
> database.
> -- Is there an effective way of stopping H2 server from the command
> line?
Use -tcpShutdownForce
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.
