Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <170BB361-8FAF-407D-AEDC-EF3C5B931117@dslextreme.com>
References: 
 <CAKSB_jPN97A7qU5Nia6PBZQKpLoz1gDn2DMqhcSCboi4-=tSuA@mail.gmail.com>
	<170BB361-8FAF-407D-AEDC-EF3C5B931117@dslextreme.com>
Date: Fri, 1 Aug 2014 15:16:29 -0400
Message-ID: 
 <CAKSB_jP+FFnbztmOMULRsfkm5F0+Dq=EFNMf4di0p6n5q=fDmA@mail.gmail.com>
Subject: Re: problems with web app and JndiContextSelector
From: Mike Calmus <mike@calmus.org>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2d2befd49bd04ff9639bf

--001a11c2d2befd49bd04ff9639bf
Content-Type: text/plain; charset=UTF-8

We're using a Servlet 2.5 container and configuration. I added the
Log4jContextSelector environment variable to the container startup as well
as loading all the Log4j 2.0 jars with the container. I added the following
items to my web.xml:

  <context-param>
    <param-name>isLog4jContextSelectorNamed</param-name>
    <param-value>true</param-value>
  </context-param>
  <context-param>
    <param-name>log4jContextName</param-name>
    <param-value>myapp</param-value>
  </context-param>
  <context-param>
    <param-name>log4jConfiguration</param-name>

<param-value>file:///${sys:projectprops}/myapp/default/log4j2.xml</param-value>
  </context-param>
  <listener>

<listener-class>org.apache.logging.log4j.web.Log4jServletContextListener</listener-class>
  </listener>
  <filter>
    <filter-name>log4jServletFilter</filter-name>

<filter-class>org.apache.logging.log4j.web.Log4jServletFilter</filter-class>
  </filter>
  <filter-mapping>
    <filter-name>log4jServletFilter</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>ERROR</dispatcher>
  </filter-mapping>
With just this, logging works fine, but I get an error when the JNDI lookup
fails.

  <env-entry>
    <description>Sets the logging context for the web-app</description>
    <env-entry-name>log4j/context-name</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>myapp</env-entry-value>
  </env-entry>
The JNDI lookup error goes away but logging stops working.

I also tried adding the following with no change in results.

  <env-entry>
    <description>URL for configuring log4j context</description>
    <env-entry-name>log4j/configuration-resource</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>

<env-entry-value>file:///${sys:projectprops}/myapp/default/log4j2.xml</env-entry-value>
  </env-entry>


On Tue, Jul 29, 2014 at 11:37 AM, Ralph Goers <ralph.goers@dslextreme.com>
wrote:

> The best would be a sample project that demonstrates the problem. At a
> minimum I would think the web.xml and log4j 2 configuration.
>
> Ralph
>
> On Jul 29, 2014, at 5:47 AM, Mike Calmus <mike@calmus.org> wrote:
>
> > I am having problems moving our web app over to Log4j 2.0 using JNDI
> > lookups. I followed the configuration documentation and am not getting
> any
> > errors, but nothing is being logged to my configured appenders. Weirdly,
> if
> > I remove the JNDI env-entry configuration from web.xml logging seems to
> > work, albeit with the expected NameNotFoundException in the server
> output.
> >
> > One possibly relevant configuration difference is that we load the log4j
> > jar files as part of server startup so each app doesn't have to load
> them.
> >
> > Any ideas? What configuration can I provide to help troubleshoot?
> >
> > Thanks.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>

--001a11c2d2befd49bd04ff9639bf--