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

Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2018/09/25 23:35:00 UTC

[jira] [Assigned] (GEODE-5780) replace the geode LoggingThreadGroup by using Thread.setUncaughtExceptionHandler

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

Darrel Schneider reassigned GEODE-5780:
---------------------------------------

    Assignee: Darrel Schneider

> replace the geode LoggingThreadGroup by using Thread.setUncaughtExceptionHandler
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-5780
>                 URL: https://issues.apache.org/jira/browse/GEODE-5780
>             Project: Geode
>          Issue Type: Improvement
>          Components: core
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>
> A long time ago geode wanted to make sure that any uncaught exceptions would be logged. This was before java 1.5 so the way we decided to do this was create thread groups for all the thread pools geode had. Each of these groups define an uncaught exception handler that would use the geode logger to log the exception.
> Since java 1.5 Thread now has setUncaughtExceptionHandler(UncaughtExceptionHandler).
> This would be simpler than creating a ThreadGroup. The geode LoggingThreadGroup actually keeps a static collection of all the groups created and it would be nice to get rid of that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)