You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2015/05/08 19:17:01 UTC

[jira] [Reopened] (ZOOKEEPER-602) log all exceptions not caught by ZK threads

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt reopened ZOOKEEPER-602:
------------------------------------

Reopening based on this Pagerduty article makes a good case for backporting this jira to 3.4.x:
http://www.pagerduty.com/blog/the-discovery-of-apache-zookeepers-poison-packet/

Thoughts?

> 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
>            Assignee: Rakesh R
>            Priority: Critical
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch
>
>
> the java code should add a ThreadGroup exception handler that logs at ERROR level any uncaught exceptions thrown by Thread run methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)