I've recently switched one of our JBoss servers from 5.0.1 to 5.1. I've noticed that the SQL connection details are being logged on a FINE level in the server.log:
2011-10-03 05:55:07,016 FINE [com.microsoft.sqlserver.jdbc.internals.XA] (JCA PoolFiller) SQLServerXADataSource:3 End get physical connection, ConnectionID:88
2011-10-03 05:55:07,016 FINE [com.microsoft.sqlserver.jdbc.internals.SQLServerDataSource] (JCA PoolFiller) SQLServerXAConnection:88 Physical connection, ConnectionID:88
2011-10-03 05:55:07,016 FINE [com.microsoft.sqlserver.jdbc.internals.SQLServerDataSource] (JCA PoolFiller) SQLServerXAConnection:88 proxy ProxyConnectionID:88 is returned.
2011-10-03 05:55:07,016 FINE [com.microsoft.sqlserver.jdbc.internals.XA] (JCA PoolFiller) XAResourceID:88 created by (SQLServerXAConnection:88)
2011-10-03 05:55:07,017 FINE [com.microsoft.sqlserver.jdbc.internals.SQLServerConnection] (JCA PoolFiller) ConnectionID:89 created by (SQLServerXADataSource:3)
My settings are the same as as on 5.0.1 in jboss-log4j.xml. I've tried adding in various combinations of the following:
<category name="com.microsoft.sqlserver.jdbc" >
<priority value="DEBUG"/>
</category>
but with no luck. I'm trying to harden everything down before we switch to production... Is there something else I need to try to avoid these cluttering up my log files?
Looks like that package use JDK logging to log those messages. JDK log level FINE == Log4j/JBoss log level DEBUG. See this mapping here http://community.jboss.org/wiki/UsageOfLoggingLevels. Change it to INFO and that should fix it.