Too much logging in JBOSS Eap 6.0.1.GA

[akaw]

My company recently migrated from ibatis to hibernate 4.2.0.Final.  Everything seems to work fine, except that the statup logging to server.log has gone crazy.  It looks like when jboss is starting up, it is setting all of our loggers to DEBUG and then wrapping them in INFO.  Here is a quick sample:

15:17:39,606 INFO  [stdout] (ServerService Thread Pool -- 58) 15:17:39.606 [ServerService Thread Pool -- 58] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.beans.factory.config.PropertyOverrideConfigurer#1'
15:17:39,606 INFO  [stdout] (ServerService Thread Pool -- 58) 15:17:39.606 [ServerService Thread Pool -- 58] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Creating instance of bean 'org.springframework.beans.factory.config.PropertyOverrideConfigurer#1'
15:17:39,607 INFO  [stdout] (ServerService Thread Pool -- 58) 15:17:39.607 [ServerService Thread Pool -- 58] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Eagerly caching bean 'org.springframework.beans.factory.config.PropertyOverrideConfigurer#1' to allow for resolving potential circular references

This is obviously generating a ton of noise in our log files and upsetting or sys admins.  I can set the startup root-logger configuration to WARN, but then I'm losing some useful messages.  The solution I want is to not let the DEBUG statements get wrapped in INFO.

Any thoughts on what is going on?  Below is logging section of standalone.xml config file that I'm using, I don't believe there are any significant changes from the distributed version.

<subsystem xmlns="urn:jboss:domain:logging:1.1">

            <console-handler name="CONSOLE">

                <level name="INFO"/>

                <formatter>

                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

                </formatter>

            </console-handler>

            <periodic-rotating-file-handler name="FILE">

                <formatter>

                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

                </formatter>

                <file relative-to="jboss.server.log.dir" path="server.log"/>

                <suffix value=".yyyy-MM-dd"/>

                <append value="false"/>

            </periodic-rotating-file-handler>

            <logger category="org.jboss.as.jpa">

                <level name="DEBUG"/>

            </logger>

            <logger category="com.arjuna">

                <level name="WARN"/>

            </logger>

            <logger category="org.apache.tomcat.util.modeler">

                <level name="WARN"/>

            </logger>

            <logger category="sun.rmi">

                <level name="WARN"/>

            </logger>

            <logger category="jacorb">

                <level name="WARN"/>

            </logger>

            <logger category="jacorb.config">

                <level name="ERROR"/>

            </logger>

            <root-logger>

                <level name="INFO"/>

                <handlers>

                    <handler name="CONSOLE"/>

                    <handler name="FILE"/>

                </handlers>

            </root-logger>

        </subsystem>

[wdfink]

Looks like that for some reason the logging of DEBUG o.s.b.f.s.DefaultListableBeanFactory is routed to STDOUT, this is catched by the JBoss logger and logged with INFO level

[akaw]

I'm not so concerned about the DEBUG statement getting routed to STDOUT so much as I don't understand why the DEBUG statement is getting generated at all.

[jamezp]

It looks like you have a log4j configuration file in your deployment. Try passing -Dorg.jboss.as.logging.per-deployment=false to disable that configuration from being used.

--

James R. Perkins

[akaw]

This helped:

http://stackoverflow.com/questions/6811341/jboss-logging-how-to-limit-un-known-classes?rq=1

I just added

<logger category="stdout">
    <level name="WARN"/>
</logger>

to my logging subsystem and those messages went away

[jamezp]

I wouldn't suggest that. You won't see any messages written to stdout at all. It really looks like you have a log4j configuration somewhere in your deployment. It's likely there is a console appender configured which is why it's writing to stdout and getting wrapped by JBoss STDIO.

--

James R. Perkins