[[I crawled the archive a bit, and wrote here as
jboss-as-dev seems inactive. If it's the wrong list here to
talk about an old version of jboss/wildfly, just let me
I was recently trying to customize the output of JBoss 7
(EAP6.1) in our development environment.
We're currently seeing what IMO is far too many logs at the
beginning of the server (about 3.5k lines, and too many logs
kills the logs :-)).
We'd like to configure the root-logger at ERROR level, and
redefine our root package at just WARN.
Then, we particularly want to keep two INFO logs from
JBoss: starting/finished starting[error or not].
[-] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) démarre
[-] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) a
démarré en 32035ms - 5898 sur 6139 services ont démarré (229
services sont passifs ou à la demande)
To achieve that, someone previously configured org.jboss.as
logger at the INFO level. BUT, as this is a parent package of
almost anything in the server, this seems to activate a lot of
other logs (some from org.jboss.as.clustering.foo,
org.jboss.as.naming.bar to name a few).
So, I naively first tried configuring the FQN being
displayed org.jboss.as.server.ApplicationServerService and
org.jboss.as.server.BootstrapListener, and realized this did
not change anything.
ApplicationServerService  and BootstrapListener, for
instance, actually log the server through the
And AS_ROOT_LOGGER is "bound" to org.jboss.as... I'm stuck.
I have to activate org.jboss.as
to see the starting logs, but at the same time enabling other
Btw, why do those logs get sent through
) instead of
ServerLogger.ROOT_LOGGER (org.jboss.as.server)? Was it
actually made on purpose?
A possible solution I see might be to redefine some
org.jboss.as.foo package at a higher level than INFO in my
standalone.xml, but this seems a bit cumbersome.
Did I understand how logging inside as/wildfly work
correctly? Do you see another way to achieve what I say above?
Thanks a lot for any hint.