[
https://issues.apache.org/jira/browse/BOOKKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893185#comment-13893185
]
Hudson commented on BOOKKEEPER-729:
-----------------------------------
SUCCESS: Integrated in bookkeeper-trunk #540 (See
[https://builds.apache.org/job/bookkeeper-trunk/540/])
BOOKKEEPER-729: Bookie shouldn't exit with 0, if exiting from deathwatcher and
thread death was caused by OOM (ivank via fpj) (sijie: rev 1565109)
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Bookie.java
> Bookie shouldn't exit with 0, if exiting from deathwatcher and thread death
> was caused by OOM
> ---------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-729
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-729
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.3.0
>
> Attachments:
> 0005-BOOKKEEPER-729-When-bookie-exits-with-an-error-and-c.patch
>
>
> I've seen the deathwatcher reset the exit code to 0, even after it was set
> correct. We should make setting the exitcode a one way operation.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
