[
https://issues.apache.org/jira/browse/LOG4J2-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090860#comment-17090860
]
Raymond DeCampo commented on LOG4J2-2823:
-----------------------------------------
Additional information - I was able to workaround the issue by using a version
of the log4j-api jar which is the Java 9 compatible code only. That is I
started with the files from /META-INF/versions/9 and then added in anything
from / with no overwriting and of course excluding /META-INF/versions/. (An
interesting maven puzzle.) So the issue is related somehow to the
multi-release jar.
> UnsupportedOperationException in WebLogic 14.1 environment
> ----------------------------------------------------------
>
> Key: LOG4J2-2823
> URL: https://issues.apache.org/jira/browse/LOG4J2-2823
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.13.1
> Environment: WebLogic 14.1.1
> JEE 8
> (Oracle) Java 11.0.6
> CentOS 7.7.1908
>
> Reporter: Raymond DeCampo
> Priority: Major
> Attachments: xyzzy.tar.gz
>
>
> When using LogManager.getLogger() in a WebLogic 14.1 environment, I get an
> UnsupportedOperationException (No class provided, and an appropriate one
> cannot be found.) The same code works fine outside of WebLogic.
>
> I have attached a maven WAR project to reproduce the error. It also
> demonstrates that the code works fine outside of WebLogic.
>
> Not sure if this is your issue or WebLogic's, but I figured I would document
> it here and see what the log4j team thinks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
