[jboss-jira] [JBoss JIRA] Created: (JBAS-4094) The following message appears every minute on the minute: [org.jboss.logging.Log4jService$URLWatchTimerTask] (Timer-0:) Configuring from URL: resource:log4j.xml

Tue Feb 13 12:00:30 EST 2007

The following message appears every minute on the minute: [org.jboss.logging.Log4jService$URLWatchTimerTask] (Timer-0:) Configuring from URL: resource:log4j.xml
----------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBAS-4094
                 URL: http://jira.jboss.com/jira/browse/JBAS-4094
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-4.0.5.CR1
         Environment: Seen on linux but probably will occur anyways.
            Reporter: Stephen Agneta
         Assigned To: Scott M Stark
            Priority: Trivial

 org.jboss.logging.Log4jService has a bug in which it will display the log message "[org.jboss.logging.Log4jService$URLWatchTimerTask] (Timer-0:) Configuring from URL: resource:log4j.xml" every minute on the minute if the log4j.xml file has a modification file that is in the FUTURE in comparison to the system clock.

The reason is because the algorithm for testing modification times is incorrect. Instance variable lastConfigured should be set to the modification time and not the current system time. The conditional below should be changed:

From:
  if (lastConfigured < lastModified)

to: 
  if ( 0 != (lastConfigured - lastModified))

This is much more robust and does not require that relative time difference be precise. Rather, we simply check if the modifcation time has changed in any way which is what is desired.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira