[
https://issues.apache.org/jira/browse/ZOOKEEPER-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593921#comment-14593921
]
Hudson commented on ZOOKEEPER-2185:
-----------------------------------
FAILURE: Integrated in ZooKeeper-trunk #2731 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2731/])
ZOOKEEPER-2185: Run server with -XX:+HeapDumpOnOutOfMemoryError and
-XX:OnOutOfMemoryError='kill %p' (Chris Nauroth via rgs) (rgs:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1686296)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/bin/zkServer.cmd
* /zookeeper/trunk/bin/zkServer.sh
* /zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml
> Run server with -XX:+HeapDumpOnOutOfMemoryError and
> -XX:OnOutOfMemoryError='kill %p'.
> -------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2185
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2185
> Project: ZooKeeper
> Issue Type: Improvement
> Components: documentation, scripts
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Fix For: 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2185.001.patch
>
>
> Continuing to run a server process after it runs out of memory can lead to
> unexpected behavior. This issue proposes that we update scripts and
> documentation to add these JVM options:
> # {{-XX:+HeapDumpOnOutOfMemoryError}} for help with post-mortem analysis of
> why the process ran out of memory.
> # {{-XX:OnOutOfMemoryError='kill %p'}} to kill the JVM process, under the
> assumption that a process monitor will restart it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
