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

Posted to dev@sling.apache.org by "Justin Edelson (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/20 20:21:38 UTC

[jira] [Resolved] (SLING-2242) UncaughtExceptionHandler should log with a better log name

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

Justin Edelson resolved SLING-2242.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: Extensions Thread Dumper 0.2.4
         Assignee: Justin Edelson
    
> UncaughtExceptionHandler should log with a better log name
> ----------------------------------------------------------
>
>                 Key: SLING-2242
>                 URL: https://issues.apache.org/jira/browse/SLING-2242
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: Extensions Thread Dumper 0.2.4
>
>
> The UncaughtExceptionHandler in the threaddump bundle uses org.apache.sling.extensions.threaddump.internal.Activator as the log name. This can create confusion because the exception being logged did not necessarily originate with or even pass through Sling.
> Thus, I recommend changing the log name to org.apache.sling.extensions.threaddump.UncaughtExceptionHandler. This keeps the package structure, but attempts to make it more obvious what is going on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira