[ 
https://issues.apache.org/jira/browse/LOG4J2-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397018#comment-16397018
 ] 

Gary Gregory commented on LOG4J2-2281:
--------------------------------------

You've sadly steeped into the mess that are Java 9's multi-release jars that 
seems to breaking everything left and right.

Nothing except Java itself should be looking into a jar's {{META-INF}} folder. 
In this particular case, you might be able to fix this by updating the 
dependency on ObjectWeb's ASM to a version that supports Java 9 byte codes. It 
might work. Emphasis on "might".

Gary

> Version 2.10 on IBM WebSphere 9
> -------------------------------
>
>                 Key: LOG4J2-2281
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2281
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API, Core
>    Affects Versions: 2.10.0
>         Environment: Tested on WebSphere 8.5 and 9.0 on Windows and z/OS
>            Reporter: Philipp Schneider
>            Priority: Blocker
>         Attachments: log4j2-2-10-on-was9.txt
>
>
> The new Log4J2 version 2.10.0 creates some really weird issues on WebSphere.
> It might be related to the split of the server components into the unreleased 
> tools project(LOG4J2-2064).
> I have attached the stacktrace of a WebSphere 9 instance on Windows 7. I hope 
> you can get anything out of it.
> It even crashes the server sometimes when I am trying to deploy from Eclipse, 
> but this might be related to the bad quality of the Eclipse plugin by IBM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to