[
https://issues.apache.org/jira/browse/ZOOKEEPER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447331#comment-13447331
]
Dawid Weiss commented on ZOOKEEPER-1544:
----------------------------------------
Yeah, looks like a duplicate, thanks Flavio.
> System.exit() calls on interrupted SyncThread
> ---------------------------------------------
>
> Key: ZOOKEEPER-1544
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1544
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.3.6
> Reporter: Dawid Weiss
> Priority: Trivial
>
> We have a test framework at Lucene/Solr which attempts to interrupt threads
> that leak out of a single class (suite) scope. The problem we're facing is
> that ZooKeeper's SyncThread is doing this:
> {code}
> >> LOG.fatal("Severe unrecoverable error, exiting", t);
> >> System.exit(11);
> {code}
> Is this terminating the JVM really needed here? Could it be made optional
> with a system property or even removed entirely? Currently it aborts the
> entire JUnit runner and prevents successive tests from continuing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
