[slf4j-dev] [JIRA] (SLF4J-390) FAILED_INITIALIZATION case in LoggerFactory.getILoggerFactory swallows root exception

QOS.CH (JIRA) noreply-jira at qos.ch
Fri Feb 24 09:27:00 CET 2017

    [ https://jira.qos.ch/browse/SLF4J-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18221#comment-18221 ] 

Andreas Sewe commented on SLF4J-390:

That’s a helpful hint; the original exception was reported to the [Automated Error Reporting tool|https://www.ctrlflow.com/automated-error-reporting/] server employed at Eclipse in the form of [this incident|[https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/4cA6tatI4va4iib3g3RRHwacICmSyfAu0YHa0JJ8qUf4GaWwg5KugwcU755i8llx|https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/4cA6tatI4va4iib3g3RRHwacICmSyfAu0YHa0JJ8qUf4GaWwg5KugwcU755i8llx)]]. Alas, there is *no* separate incident for the original exception – either because the user didn’t consent to sending it or (more likely) because this first error didn’t hit the Eclipse Error Log but was swallowed somewhere along the way. Hence, having all the context available in a single Throwable is IMHO still preferable.

> FAILED_INITIALIZATION case in LoggerFactory.getILoggerFactory swallows root exception
> -------------------------------------------------------------------------------------
>                 Key: SLF4J-390
>                 URL: https://jira.qos.ch/browse/SLF4J-390
>             Project: SLF4J
>          Issue Type: Bug
>    Affects Versions: 1.7.22
>            Reporter: Andreas Sewe
>            Assignee: Ceki Gülcü
>            Priority: Minor
>             Fix For: 1.7.24
> I have a hard time triaging an {{IllegalStateException}} thrown by {{LoggerFactory.getILoggerFactory}} that has been reported by a user ([Eclipse Bug 510487|https://bugs.eclipse.org/bugs/show_bug.cgi?id=510487]) as the root exception is not wrapped by the {{IllegalStateException}}: [https://github.com/qos-ch/slf4j/blob/v_1.7.22/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java#L422].
> AFAICT, that exception is only logged to the console ([https://github.com/qos-ch/slf4j/blob/v_1.7.22/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java#L194]). This makes error reports sent by an automatic error reporting system (like the one employed for the Eclipse IDE) less useful, as the crucial information won't be included automatically.
> Hence, it would be great if SLF4J could hold onto the {{Throwable}} for a bit and than wrap it in the final {{IllegalStateException}}.

This message was sent by Atlassian JIRA

More information about the slf4j-dev mailing list