[
https://issues.apache.org/jira/browse/LOG4J2-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928943#comment-16928943
]
Ralph Goers commented on LOG4J2-2690:
-------------------------------------
Yeah, at this point you are right. I will work on getting an integration test
so I can fix this and validate it is going to work.
> Custom appenders no longer found with Java 11
> ---------------------------------------------
>
> Key: LOG4J2-2690
> URL: https://issues.apache.org/jira/browse/LOG4J2-2690
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.12.1
> Environment: Java 11.2
> {noformat}
> compile group: 'org.slf4j', name: 'slf4j-api', version: '1.8.0-beta4'
> compile 'org.apache.logging.log4j:log4j-slf4j18-impl:2.12.1'
> compile 'org.apache.logging.log4j:log4j-jcl:2.12.1'
> compile 'org.apache.logging.log4j:log4j-api:2.12.1'
> compile 'org.apache.logging.log4j:log4j-core:2.12.1'{noformat}
> Reporter: Tobias Diez
> Priority: Major
>
> After upgrading to Java 11, the custom appenders are no longer found. The
> following errors are shown when running the app:
> {noformat}
> 2019-09-10 21:44:54,195 main ERROR Error processing element GuiAppender
> ([Appenders: null]): CLASS_NOT_FOUND
> 2019-09-10 21:44:54,240 main ERROR Appenders contains an invalid element or
> attribute "OurApplicationInsightsAppender"
> 2019-09-10 21:44:54,261 main ERROR Unable to locate appender
> "applicationInsightsAppender" for logger config "root"
> 2019-09-10 21:44:54,262 main ERROR Unable to locate appender "GuiLogger" for
> logger config "org.jabref"
> 2019-09-10 21:44:54,262 main ERROR Unable to locate appender "GuiLogger" for
> logger config "org.apache.pdfbox"{noformat}
> The log4j config file can be found here:
> https://github.com/JabRef/jabref/blob/master/src/main/resources/log4j2.xml
> and the appender here:
> https://github.com/JabRef/jabref/blob/master/src/main/java/org/jabref/gui/logging/GuiAppender.java
> (They were working with Java 8, so it shouldn't be a configuration problem.)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
