[
https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742657#comment-13742657
]
Nick Williams commented on LOG4J2-344:
--------------------------------------
I thought about it, but doing so makes me nervous. This would mask
implementation problems in the container. If thousands of Log4j users complain
to WebLogic because their applications won't work, such a bug is going to get
fixed really quickly...
I think we should probably contact Oracle and report the problem and see
whether we think they'll act on it in a reasonable timeframe before we make
such a move.
*Important*
I suppose it's _possible_ there's something wrong with
{{org.apache.logging.log4j.core.web.Log4jWebInitializerImpl#getLog4jWebInitializer(ServletContext)}},
such that it can return a {{null}} value, but:
# Reading the code a again, I can't for the life of me understand how it could
possibly return {{null}}; and,
# If it did return {{null}}, we should also be seeing an NPE from line 52 in
{{init}}.
> Log4j2 doesnt work with Weblogic 12c
> ------------------------------------
>
> Key: LOG4J2-344
> URL: https://issues.apache.org/jira/browse/LOG4J2-344
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0-beta8
> Environment: Windows XP SP 3
> Reporter: Keir
>
> I get a "Context destroyed before it was initialized" exception, the problem
> seems to be that the servlet filters init method is not being called by
> WebLogic, not sure why...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
