socket timeout problem

Bug #744053 reported by Nik Klever on 2011-03-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rocket Web Server

Bug Description

Hi Tim,

I'm using web2py since two years. Web2py is using your rocket server since 1.77. The Behaviour of your rocket server changed from Version 1.06a (1.89.5 in Web2py) to 1.21, 1.22 and 1.23 as shown in the following files.

I've used a simple test script "" which imports rocket and logs on rocket_xxx.log.

I've made a simple connection using telnet which is logged by script files rocket_test_xxx.

The difference between the Version 1.06a and 1.2x is a socket timeout which leads to a 500 server error. In normal usage this socket timeout is normally not relevant because socket connections are below 1 sec. But using telnet and manually typing the HTTP-GET-Request shows this bug clearly. This timeout ignores the timeout value of 600 sec (as the default) in the init of the rocket server.

I hope you can reproduce the error and find out the problem.


Nik Klever (nik-klever) wrote :
Tim (tdfarrell) wrote :

Thanks Nik,

I'll take a look at this over the next several days. Thank you for providing a test!


Changed in rocket:
importance: Undecided → Medium
Tim (tdfarrell) wrote :

I've committed a fix in #193. Thanks for pointing this out.

Changed in rocket:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers