[
https://issues.apache.org/jira/browse/LOG4J2-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459257#comment-17459257
]
Manjunath DS commented on LOG4J2-3201:
--------------------------------------
Did any one face this issue, upgraded to version log4j2 1.6 in weblogic 12c
(added these 3 class files log4j-core-2.16.0.jar, log4j-slf4j-impl-2.16.0,
log4j-api-2.16.0.jar)
(replaced existing log4j-core-2.15.0.jar, log4j-slf4j-impl-2.15.0,
log4j-api-2.15.0.jar)
log4j2 is used with slf4j-api-1.6.0.jar
Exception in thread "pool-4-thread-1" java.lang.NoClassDefFoundError:
org/apache/logging/log4j/message/ParameterizedNoReferenceMessageFactory$StatusMessage
at
org.apache.logging.log4j.message.ParameterizedNoReferenceMessageFactory.newMessage(ParameterizedNoReferenceMessageFactory.java:105)
at
org.apache.logging.log4j.message.AbstractMessageFactory.newMessage(AbstractMessageFactory.java:75)
at
org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2010)
at
org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1884)
at
org.apache.logging.log4j.spi.AbstractLogger.error(AbstractLogger.java:793)
at
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:76)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.message.ParameterizedNoReferenceMessageFactory$StatusMessage
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:387)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:348)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:86)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at
weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:193)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:52)
... 7 more
> Limit the protocols jNDI can use and restrict LDAP.
> ---------------------------------------------------
>
> Key: LOG4J2-3201
> URL: https://issues.apache.org/jira/browse/LOG4J2-3201
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: Ralph Goers
> Priority: Major
> Fix For: 2.15.0
>
>
> LDAP needs to be limited in the servers and classes it can access. JNDI
> should only support the java, ldap, and ldaps protocols by default.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
