logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remko Popma <remko.po...@gmail.com>
Subject Re: Logging stops on application redeploy
Date Thu, 28 Jul 2016 22:50:55 GMT
That last paragraph: debug disabled, errors go to the console, sounds like the behavior you
get when Log4j2 can't find a configuration file. 

I wonder how redeploy could cause Log4j to become unable to find the configuration...

What do you see when you enable Log4j internal status logging? https://logging.apache.org/log4j/2.x/faq.html#troubleshooting


Sent from my iPhone

> On 2016/07/29, at 5:30, Mike Calmus <mike@calmus.org.INVALID> wrote:
> We are having issues with Log4j (many versions up to and including 2.6.2)
> where it works fine when an application is newly deployed and at server
> startup but where logging stops when an application is redeployed.
> We are using JBoss EAP 6. Applications are configured as Servlet 3.0 and we
> are using named JNDI context selectors.
> Log4j is being loaded from a JBoss module rather than being bundled with
> each application. This module has core, api, web, jcl, jul and api-1.2.
> We are not sure if this is an EAP issue or a log4j issue, but I thought I'd
> post to see if anyone had any ideas.
> Using a debugger I'm seeing that standard calls to log4j returning false
> for such things as "isDebugEnabled". Errors and such go to the JBoss
> console for these apps as though the standard configuration is being used.

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

View raw message