You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2010/08/10 06:29:05 UTC

DO NOT REPLY [Bug 49732] New: reply_timeout can't wait forever.

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

           Summary: reply_timeout can't wait forever.
           Product: Tomcat Connectors
           Version: 1.2.30
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_jk
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: yoshihara.ryuiti@oss.ntt.co.jp


Created an attachment (id=25869)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=25869)
Log and configuration for this mod_jk's test

I tested following JSP file on the Tomcat.


<%
  try {
    Thread.sleep(10000);
  } catch (Exception e) {}
%>
<html>
<head><title>Timeout</title></head>
<body>Timeout</body>
</html>


 workers.properties configuration was following:

worker.list=ap1

worker.template.type=ajp13
worker.template.port=8009
worker.template.lbfactor=1
worker.template.socket_timeout=5
worker.template.connect_timeout=3000
worker.template.prepost_timeout=3000
worker.template.recovery_options=3

worker.template.reply_timeout=0

worker.ap1.reference=worker.template
worker.ap1.host=127.0.0.1
worker.ap1.port=8009


***


 For mod_jk 1.2.22, Apache access_log was followig after this test.

127.0.0.1 - - [05/Aug/2010:14:11:41 +0900] "GET /ap001/timeout.jsp HTTP/1.1"
200 73 11163952


 For mod_jk 1.2.30, Apache access_log was followig after this test.

127.0.0.1 - - [05/Aug/2010:11:44:17 +0900] "GET /ap001/timeout.jsp HTTP/1.1"
502 306 7007548


 Reference Guide say

  http://tomcat.apache.org/connectors-doc/reference/workers.html
  reply_timeout
  > By default (value zero) the webserver will wait forever which could be an
issue for you.

 However, I guess mod_jk 1.2.30 does not wait for response forever.

 I think influence of following fix.
 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_connect.c?view=markup&pathrev=705977


 Best regards

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


DO NOT REPLY [Bug 49732] reply_timeout can't wait forever.

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49732

Konstantin Kolinko <kn...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|yoshihara.ryuiti@oss.ntt.co |dev@tomcat.apache.org
                   |.jp                         |

--- Comment #3 from Konstantin Kolinko <kn...@gmail.com> 2010-11-01 05:24:13 EDT ---
Reverted "Assigned To" field to the default value.
Please, do not change it.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


DO NOT REPLY [Bug 49732] reply_timeout can't wait forever.

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49732

Rainer Jung <ra...@kippdata.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Rainer Jung <ra...@kippdata.de> 2010-08-10 17:04:02 EDT ---
I expect this is a side effect of your socket_timeout. Remove it and retest. If
there still is an issue, you can reopen the ticket. Please do attach a debug
log file then.

Some more information about timeouts is contained in

http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html

Regards,

Rainer

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


DO NOT REPLY [Bug 49732] reply_timeout can't wait forever.

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49732

Ryuichi Yoshihara <yo...@oss.ntt.co.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |
         AssignedTo|dev@tomcat.apache.org       |yoshihara.ryuiti@oss.ntt.co
                   |                            |.jp

--- Comment #2 from Ryuichi Yoshihara <yo...@oss.ntt.co.jp> 2010-11-01 04:14:53 EDT ---
Created an attachment (id=26244)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26244)
Patch of "jk_ajp_common.c" and "jk_connect.c"

 Surely, remove socket_timeout, wait forever.
 However, socket_timeout influences all of connections.
 I want it to wait forever only when the response is returned from Tomcat.

 I made patch.

 Best regards.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


[Bug 49732] reply_timeout can't wait forever.

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49732

Rainer Jung <ra...@kippdata.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEEDINFO

--- Comment #4 from Rainer Jung <ra...@kippdata.de> ---
The general socket_timeout is not recommended exactly because of its side
effects. We do have individual timeouts for the connection setup, the
cping/cpong, the reply and the connection idle time. So why do you think you
still need to use the general socket_timeout?

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

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