On Wed, 2013-04-24 at 18:03 +0200, Mark Miller wrote: > On Apr 24, 2013, at 12:00 PM, Mark Miller <markrmil...@gmail.com> wrote: > > >> -XX:OnOutOfMemoryError="kill -9 %p" -XX:+HeapDumpOnOutOfMemoryError > > The way I like to handle this is to have the OOM trigger a little script or > set of cmds that logs the issue and kills the process.
We treat all Errors as fatal by writing to a dedicated log and shutting down the JVM (which triggers the load balancer etc.). Unfortunately that means that some XML + XSLT combinations can bring the JVM down due to StackOverflowError. This might be a little too diligent as the Oracle JVM running on Linux (our current setup) is resilient to Threads hitting stack overflow. - Toke Eskildsen, State and University Library, Denmark
