You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Volkan Yazici (Jira)" <ji...@apache.org> on 2022/05/02 21:13:00 UTC
[jira] [Closed] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype
[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Volkan Yazici closed LOG4J2-3463.
---------------------------------
Resolution: Fixed
> java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3463
> URL: https://issues.apache.org/jira/browse/LOG4J2-3463
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Core, Log4j 1.2 bridge, Web/Servlet
> Affects Versions: 2.17.3
> Environment: Configuration:
> Using bridge api 2.17.3 latest snapshot. Also using log4j-web, log4j-api, log4j-core (all 2.17.3 snapshot). A wrapper class is used for configuration across applications running on tomcat.
> Reporter: Swapnil Markhedkar
> Priority: Blocker
> Fix For: 2.18.0
>
> Attachments: Provider error.txt
>
>
> Came across this error while using tomcat at application level. Similar to https://issues.apache.org/jira/browse/LOG4J2-2055, but error persists even when added 2.10 jars.
> In depth stack trace has been attached as text file.
> NOTE: Tomcat server and it's logging is working fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)