Did a bit of research on Jira - this is issue
LOG4J2-359<https://issues.apache.org/jira/browse/LOG4J2-359>
On Tue, Jan 21, 2014 at 11:15 AM, Dave Levitt wrote:
> I'm trying to add log4j 2.x to a Servlet 2.5 web app.
>
> One goal is to also be able to deploy the artif
I'm trying to add log4j 2.x to a Servlet 2.5 web app.
One goal is to also be able to deploy the artifact on a Servlet 3.x
container as the servers are migrated [from JBoss 5.x to 7].
When testing on JBoss 7.1, an exception is thrown from
Log4jServletContainerInitializer [line 49] as the servlet c
Wouldn't that application be the sort of thing to use 'nested
diagnostic context' on?
NDC.push("filterable trans start message");
and pop the context in the 'finally' after the commit or rollback.
On 6/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
In my application, I wanted to use
ange maybe you can
persuade them to follow the best practices for libraries which
strongly discourage explictit configuration. There is discussion
about this in the archives.
Setting up repository selectors might be helpful.
On 3/21/07, Dave Levitt <[EMAIL PROTECTED]> wrote:
> I was tr
I was trying to find out where my logging output was going in a J2EE
application [WebSphere _and_ ATG Dynamo - things just don't get any
uglier than that]
When I enabled log4j.debug, I saw that the log4j system was being
initialized twice, once by my log4j.xml and a second time from a
log4j.prope
