[
https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774594#comment-13774594
]
Nick Williams commented on LOG4J2-344:
--------------------------------------
Thanks for discovering this, Tomasz! I don't have access to a WebLogic
environment, so it's hard for me to troubleshoot. I _suspect_ that WebLogic's
behavior here is a violation of the spec (reasoning: it would be invalid to
initialize the filter at the time you call {{addFilter}}, because the filter is
supposed to be initialized at a later phase of the application lifecycle).
However, now it looks like we have a non-hacky approach to solving this problem.
Can you try out one thing for me? I'm wondering if using {{addFilter(String
filterName, Class<? extends Filter> filterClass)}} works as well. This would be
preferable, as it would be more compile safe. Let me know whether that works,
and then I'll make the change.
> 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
> Attachments: web.xml
>
>
> 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]
