You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Tomasz Wladzinski (JIRA)" <ji...@apache.org> on 2013/09/23 14:13:02 UTC

[jira] [Comment Edited] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

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

Tomasz Wladzinski edited comment on LOG4J2-344 at 9/23/13 12:11 PM:
--------------------------------------------------------------------

I had the same issue. My investigation showed that when you add servlet filter using ServletContext.addFilter(java.lang.String filterName, Filter filter) WebLogic does not invoke filter's init method. Most probably assuming that you were to do it as you created the instance. When I changed it to addFilter(java.lang.String filterName, java.lang.String className) everything worked in order.
                
      was (Author: spacetom):
    I had the same issue. My investigation showed that when you add servlet filter using ServletContext.addFilter(java.lang.String filterName, Filter filter) WebLogic does not invoke filter's init method. Most probably assuming that you were to do it as you created the instance. When I changed it to addFilter(addFilter(java.lang.String filterName, java.lang.String className)) everything worked in order.
                  
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org