zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "maoling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1442) Uncaught exception handler should exit on a java.lang.Error
Date Sat, 29 Jul 2017 14:35:02 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106137#comment-16106137

maoling commented on ZOOKEEPER-1442:

This uncaught exception runs so fast that we spent five years to try to catch it

> Uncaught exception handler should exit on a java.lang.Error
> -----------------------------------------------------------
>                 Key: ZOOKEEPER-1442
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1442
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client, server
>    Affects Versions: 3.4.3, 3.3.5
>            Reporter: Jeremy Stribling
>            Assignee: Jeremy Stribling
>            Priority: Minor
>         Attachments: ZOOKEEPER-1442.patch, ZOOKEEPER-1442.patch, ZOOKEEPER-1442.patch
> The uncaught exception handler registered in NIOServerCnxnFactory and ClientCnxn simply
logs exceptions and lets the rest of ZooKeeper go on its merry way.  However, errors such
as OutOfMemoryErrors should really crash the program, as they represent unrecoverable errors.
 If the exception that gets to the uncaught exception handler is an instanceof a java.lang.Error,
ZK should exit with an error code (in addition to logging the error).

This message was sent by Atlassian JIRA

View raw message