Reconfiguration should take place if the file timestamp is newer than what it was at startup or the last reconfiguration. It is only checked for once for every 16 log events written if the interval has expired. If the app doesn’t write many events then it might not ever reconfigure. Using a watchdog would definitely fix that.
Ralph > On Jul 31, 2015, at 1:49 PM, Gary Gregory <[email protected]> wrote: > > Hi All: > > I have a case where I: > - start my app with INFO level logging > - wait an hour > - update and save the log4j config file (which already had > monitorInterval="5") to use DEBUG and Console logging in addition to the > already configured rolling file. > - no config changes seem to take effect. > > I know the app is running with one thread and that thread is very busy > reading MBs upon MBs of data from a socket input stream, which I can confirm > my peeking at the app from VisualVM. > > Would using a Java 7 file watchdog make reconfiguration more reliable? > > Gary > > -- > E-Mail: [email protected] <mailto:[email protected]> | > [email protected] <mailto:[email protected]> > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> > Home: http://garygregory.com/ <http://garygregory.com/> > Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
