[
https://issues.apache.org/jira/browse/UIMA-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872672#action_12872672
]
Jörn Kottmann commented on UIMA-1789:
-------------------------------------
No, dumping the memory when an OutOfMemoryError occurs makes it possible to
analyze the issue
afterwards, if the system is set up correctly (so its not crashing directly
after startup) a memory leak can cause an OOME after maybe a few weeks of
operation. In my opinion thats why you want to dump the memory on an OOME in a
production environment, when the system fails its possible
to analyze the cause directly afterwards. If its not dumped, you maybe have to
wait for a few days until its clear in the memory dump (e.g. taken with jmap or
gcore), where the leak is.
If its possible it would be nice to have this option in the script as a default.
> deployAsyncService script should use -XX:+HeapDumpOnOutOfMemoryError
> --------------------------------------------------------------------
>
> Key: UIMA-1789
> URL: https://issues.apache.org/jira/browse/UIMA-1789
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jörn Kottmann
> Priority: Minor
>
> In case a user application needs to much memory an OuOfMemoryError stops the
> UIMA AS service. It would
> be nice if the VM would just dump the memory for further analysis and stops
> afterwards.
> For a sun vm this can be achieved with this command line option:
> -XX:+HeapDumpOnOutOfMemoryError
> Can this be done in our script, does it also work with other VMs ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
