[
https://issues.apache.org/jira/browse/UIMA-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874331#action_12874331
]
Marshall Schor commented on UIMA-1789:
--------------------------------------
Another potential issue is that this parameter is one of the XX ones, which
means it is likely not standard for all JVMs. For instance, the IBM JVM
doesn't have this option - see
http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/index.jsp and search on
-XX.
Another danger for users is that they would not expect this to be enabled by
default. This means that they could become puzzled by very long termination
events (in the case they were using a 64-bit OS and running with very large
heaps), or run out of disk space, etc.
My opinion is that the right diagnosis strategy for an OutOfMemory error is
probably situation dependent, and only some of them (on some JVMs) would
warrant a heap dump. So I think this should be left to developers to specify
explicitly (if their JVM supports it), and not enabled by 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.
