[Barracuda-commit] CVS Update: BarracudaDiscRack

[jacobk@xxxxxxxxxxxxxxxx]

CVSROOT:        /var/cvs
Module name:    BarracudaDiscRack
Repository:     BarracudaDiscRack/WEB-INF/
Changes by:     jacobk@xxxxxxxxxxxxxxxxx(none)  03/08/18 13:39:02

Modified files:
        BarracudaDiscRack/WEB-INF/: sample.web.xml 

Log message:
        Setting log4j-cron to default to 0 because...
        http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22478
        
        <quote name="Ceki Gulcu">
        The watchdog code in log4j 1.2.x does not have a notion of a
        lifecycle. In particular, LogManager.shutdown does not stop the 
watchdog thread.
        Atually, I don't think there is a way to stop a watchdog thread which 
is
        definetely a serious shortcoming of log4j watchdogs.
        <quote>
        
        Essentially, this means that using configureAndWatch() in a container 
will result in watchdog threads accessing dead classloaders if the 
application is stopped, but the container continues to run.  The application 
seems to survive any errors this causes, but we should probably not be using 
configureAndWatch() by default because of this issue.
        
        Jake

===================================================================
File: sample.web.xml    Status: Up-to-date

   Working revision:    1.6     Mon Aug 18 19:39:00 2003
   Repository revision: 1.6     
/var/cvs/BarracudaDiscRack/WEB-INF/sample.web.xml,v

   Existing Tags:
        BarracudaDiscRack_1_2_0         (revision: 1.4)
        jrk_20030205                    (revision: 1.1)
        jrk_20030203                    (revision: 1.1)