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. Then if you have the process supervised (via runit or something), it will just start back up (what else do you do after an OOM?), but you will have logged something, triggered a notification, whatever. - Mark
