[
https://issues.apache.org/jira/browse/LOG4J2-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Schneider resolved LOG4J2-2281.
---------------------------------------
Resolution: Workaround
Ok this seems to be a bug in WebSphere's annotation scan algorithm. As I've
learned now you can put jars and packages on the ignore list and this will help
you as a workaround.
The issue has been fixed in WebSphere 8.5.5.14 or 9.0.0.7
You can see the documentation of WebSphere's issue on IBM's website:
[http://www-01.ibm.com/support/docview.wss?uid=swg1PI89708
]Thanks for your help and leading me into the right direction 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)
