I am intentionally using my own log4j.jar and my own logging configuration in a web app.
That works great, up until a request that happens to the JBoss connection manager -- after which point the web app uses JBoss logging rather than my application's log4j configuration!
The issue seems linked to the occurrence of an exception in acquiring a DB connection:
2014-08-06 06:47:06,779 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default task-100) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
In some cases I get log4j "no appenders" warnings, etc, right before this exception is logged and in other cases I don't.
Clearly the application's logging should not go awry any time the JDBC pool cannot acquire a connection. Yet something seems to permanently puncture my application's isolated logging environment.
Has anyone seen anything like this before? Any ideas?
This is with an 8.0.0 instance patched to 8.1.0.
Nevermind. This turned out to be purely a library behaving really badly, trouncing our log4j configuration in such a way that initially looked like a reversion to JBoss' logging, but wasn't.