tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46666] New: Why is disableUploadTimeout and KeepAliveTimeout correlated in Http11 Connector?
Date Wed, 04 Feb 2009 16:28:36 GMT

           Summary: Why is disableUploadTimeout and KeepAliveTimeout
                    correlated in Http11 Connector?
           Product: Tomcat 6
           Version: 6.0.18
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connectors


        while (started && !error && keepAlive) {

            // Parsing the request header
            try {
                if (!disableUploadTimeout && keptAlive) {
                    if (keepAliveTimeout > 0) {
                    else if (soTimeout > 0) {
                keptAlive = true;
                if (!disableUploadTimeout) {

disableUploadTimeout  - This flag allows the servlet container to use a
different, longer connection timeout while a servlet is being executed, which
in the end allows either the servlet a longer amount of time to complete its
execution, or a longer timeout during data upload. If not specified, this
attribute is set to "true".

The code above is waiting on a new Http Request and precedes the servlet
processing logic.  It seems odd to me that I must set disableTimeout to false
to get my keepAliveTimeout set.  

To set keepalivetimout, I must implicitely enable upload timeout whether I need
it or not.  It seems to me that the disableTimeout is unneccessary in the
following line

if (!disableUploadTimeout && keptAlive) {

Do you agree with this?

Thanks for the insight

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message