[
https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742334#comment-13742334
]
Gary Gregory edited comment on LOG4J2-344 at 8/16/13 8:56 PM:
--------------------------------------------------------------
Hm... it looks like the {{initializer}} is null. We must have one of:
# The thread that assigned the filter's {{initializer}} is different from the
thread calling {{doFilter()}} and the change to {{initializer}} is not visible
to the {{doFilter()}} thread, making the initializer volatile may be required.
# A race condition whereby the filter's init method is not done before doFilter
is called from a different thread.
was (Author: garydgregory):
Hm... it looks like the {{initializer}} is null. We must have one of:
- The thread that assigned the filter's {{initializer}} is different from the
thread calling {{doFilter()}} and the change to {{initializer}} is not visible
to the {{doFilter()}} thread, making the initializer volatile may be required.
- A race condition whereby the filter's init method is not done before doFilter
is called from a different thread.
> 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]
