https://issues.apache.org/bugzilla/show_bug.cgi?id=54444

            Bug ID: 54444
           Summary: JULI Tomcat 6 settings for FileHandler.limit is
                    ignored.
           Product: Tomcat 6
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: sferich...@gmail.com
    Classification: Unclassified

Description of problem:

catalina.org.apache.juli.FileHandler.limit = 10000 

Seems to be ignored when a setting is applied to it.
As a result your logs grow our of control and do not roll over.

.limit .count do not seem to work for JULI org.apache.juli.FileHandler.limit &
.count are not mentioned on the Tomcat docs 

[0]
http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/juli/FileHandler.html

Documentation shows it can be configured to rotate once a day, but not using
limit or count as you would with Java Util's FileHandler.

[1] http://docs.oracle.com/javase/6/docs/api/java/util/logging/FileHandler.html

Isn't Juli supposed to be an extension of the Java Util FileHandler to expand
on its capabilities. 

WAR used to reproduce:
    https://github.com/kylape/support-examples/tree/master/fillMyLogsPlease.war

Command used to reproduce: 
    for x in {1..20}; \
        do curl --head http://localhost:8080/fillMyLogsPlease/logging; \        
        sleep 1; \
    done

To see the issue simply 
    watch ls -lah logs             << watch the size go to 14M > 10M setting.

Should there be a documentation note made on [0] and/or [1] to denote that
.limit and .count can not be used with JULI or should JULI truly extend this
functionality of Java Util.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to