[
https://issues.apache.org/jira/browse/LOG4J2-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516674#comment-17516674
]
Piotr Karwasz commented on LOG4J2-3464:
---------------------------------------
Hello [~smarkhedkar],
Your application must be picking up {{log4j-1.2-api}} from somewhere else.
Probably a pre-2.17.2 version.
> java.lang.NoSuchMethodException:
> org.apache.log4j.helpers.UtilLoggingLevel.toLevel
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-3464
> URL: https://issues.apache.org/jira/browse/LOG4J2-3464
> 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
> Attachments: To Level error.txt
>
>
> Came across this error while using tomcat at application level. In depth
> stack trace has been attached as text file.
>
> Possibly linked to [LOG4J2-3463] java.util.ServiceConfigurationError:
> org.apache.logging.log4j.spi.Provider: Provider
> org.apache.logging.log4j.core.impl.Log4jProvider not a subtype - ASF JIRA
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
