zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Reed (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-602) log all exceptions not caught by ZK threads
Date Fri, 04 Dec 2009 19:31:20 GMT

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

Benjamin Reed commented on ZOOKEEPER-602:
-----------------------------------------

i think the best strategy to address this would be to create a ZooKeeperThread that all the
code must use with the following properties:

1) it has a single constructor ZooKeeperThread(String threadName, long sid, boolean isUnhandledExceptionFatal),
where threadName is a descriptive string, sid is the server id or -1 if not relevant,

2) exceptions will be logged as errors unless isUnhandledExceptionFatal is true, then an unhandle
exception on that thread will be logged as fatal and cause a shutdown.


> log all exceptions not caught by ZK threads
> -------------------------------------------
>
>                 Key: ZOOKEEPER-602
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-602
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: java client, server
>    Affects Versions: 3.2.1
>            Reporter: Patrick Hunt
>            Priority: Critical
>             Fix For: 3.3.0
>
>
> the java code should add a ThreadGroup exception handler that logs at ERROR level any
uncaught exceptions thrown by Thread run methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message