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?
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
