-
1. Re: in logging, root-logger level is ignored
centecbertl May 4, 2013 5:17 AM (in response to andrius.karpavicius)I encountered that behaviour when updating the JDK version running JBoss from 1.7.0_09 to 1.7.0_21 (64 bit Windows versions):
- Logging was working as expected when using JDK 1.7.0_09,
- Update of JDK to 1.7.0_21 (no other change to the JBoss setup/deployments/modules,....) -> All Loggers inheriting from the Root Logger started to log in Trace level
- Downgrade to JDK JDK 1.7.0_09, -> Logging working as expected again
My Environment: Windows 7 Pro, JDK version 64 bit
No extra log4j or java logging configuration is contained in the applications modules, ear and rar files.
Unfortunately I had no chance to investigate this in more detail up to now.
-
2. Re: in logging, root-logger level is ignored
jamezp May 6, 2013 1:44 PM (in response to andrius.karpavicius)I don't know of any reason why a logger level, root or otherwise, would be ignored. Can you give some example output of incorrect log records being printed?
--
James R. Perkins
-
3. Re: in logging, root-logger level is ignored
jamezp May 6, 2013 1:46 PM (in response to centecbertl)That seems interesting. Could you provide a little more detail on what your configuration was? Like what was the root level set at, were you using a logging facade, etc.
--
James R. Perkins
-
4. Re: in logging, root-logger level is ignored
andrius.karpavicius May 7, 2013 12:35 AM (in response to jamezp)The configuration part of loging in standalone.xml is in the post above.
I tried running jboss without my application, and with a simple JSF2 application and root logger levels are working even with java 1.7.17. So foundation is fine. Now need to figure what is in my application that is causing the problem.