Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
From: Ralph Goers <ralph.goers@dslextreme.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: loggerContext for container shared lib
Date: Wed, 4 Oct 2017 20:56:36 -0700
References: <pony-55153b435ccd038857419ff38618bdbb12f7be5d-f011c01af366c890715e6ac9b244e3ed26f6d4aa@log4j-user.logging.apache.org>
To: Log4J Users List <log4j-user@logging.apache.org>
In-Reply-To: <pony-55153b435ccd038857419ff38618bdbb12f7be5d-f011c01af366c890715e6ac9b244e3ed26f6d4aa@log4j-user.logging.apache.org>
Message-Id: <2CA8C0EC-BB67-411D-8FBC-1458B0A3920B@dslextreme.com>
archived-at: Thu, 05 Oct 2017 03:56:53 -0000

You didn=E2=80=99t say if you also have a log4j2.xml file in tomcat/lib. =
If you log something before the two web apps start I am certain that it =
would use the log4j2.xml in tomcat/lib. I will have to look at the code =
that loads the configuration file to determine which ClassLoader it will =
use when the call is made from a web app. If it uses the thread context =
class loader then that could cause the problem.

Ralph

> On Oct 4, 2017, at 3:13 PM, billokara@gmail.com wrote:
>=20
> Hi,
>=20
> we have multiple webapps, say, webapp1 and webapp2, that use a shared =
apache lib (say commonLib, which also uses log4j logging) that deployed =
as jndi resource in tomcat (thus was put in tomcat/lib), and followings =
are our log4j jars deploy location:
>=20
> tomcat/lib:
> - log4j-core.jar, log4j-api.jar
> - commonLib.jar
>=20
> webapp1 and webapp2, in /WEB-INF:
> - classes/log4j2.xml
> - lib/log4j2-web.jar
>=20
> When loading, the ClassLoaderContextSelector correctly uses the =
webappClassloader to load the log4j config for webapp1 and webapp2. But =
for the commonLib loggerContext, depending on which webapp got loaded =
first, the commonLib loggerContext will either be using=20
> webapp1/WEB-INF/classes/log4j2.xml
> or=20
> webapp2/WEB-INF/classes/log4j2.xml
>=20
> This poses the problem that if say the commonLib loggerContext is =
using=20
> webapp1/WEB-INF/classes/log4j2.xml
>=20
> then webapp1 got undeployed, then the commonLib loggerContext will be =
referencing a no longer existed config file.
>=20
> any advise on how to handle or resolve the config issue for shared lib =
loggerContext that uses log4j?
>=20
>=20
> Thanks!
> Bill
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>=20
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org