Could you please post the internal status messages? More in-line. On 13.04.2013 09:53, KNair wrote:
Our application is not coupled with logback during compile time, so it wont be possible to do StatusPrint for me. But i feel ReConfigurationFilter is active, as every time my debugger catch it, i can see next fire time is set.
The debug="true" configuration directives enables output of internal status messages. You do not need to invoke StatusPrinter directly from your code. Please read the whole section, *all* twelve or so paragraphs in http://goo.gl/oR9SL Status messages give important clues as whether ReconfigureOnChangeFilter is installed, active (started=true), the actual files it is scanning as well as the scanning frequency. Are there any *status* messages by ReconfigureOnChangeFilter ? If not, it may mean that ReconfigureOnChangeFilter has not been installed, probably because there is another logback.xml configuration file picked up before your intended logback.xml configuration file. Quoting from the documentation: In the absence of status messages, tracking down a rogue logback.xml configuration file can be difficult, especially in production where the application source cannot be easily modified. To help identify the location of a rogue configuration file, you can set a StatusListener via the "logback.statusListenerClass" system property (defined below) to force output of status messages. The "logback.statusListenerClass" system property can also be used to silence output automatically generated in case of errors. To track a rogue configuratoin file, you should to set the "logback.statusListenerClass" system property to "ch.qos.logback.core.status.OnConsoleStatusListener" as explained at http://logback.qos.ch/manual/configuration.html#logback.statusLC
By setting debug = true , it prints Log statements during start time, yes there are some logs like 12:48:40,693 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. After this, there is no more INFO statement from joran packages printed when i change logger level.
I m still waiting for my other application to reach 2^16 logging statements
We are not sadists. :-) It would be ridiculous to ask users to log 65536 times for auto-scanning to be active. The 2^16 limit is reached dynamically in *extremely* busy systems just after a few seconds. Under regular load, the limit is much lower and corresponds to just a few seconds of logging. I suspect that there is something else going on, for example that there is another rogue logback.xml configuration file in your setup.
Thanks for the quick response.
K Nair
-- Ceki 65% of statistics are made up on the spot