[ grinder-Bugs-3023985 ] Bug 2919190 - setTimeout - not fixed

Bugs item #3023985, was opened at 2010-07-01 19:03
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3023985&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: HTTP Plugin
Group: None
>Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Philip Aston (philipa)
Summary: Bug 2919190 - setTimeout - not fixed

Initial Comment:
Environment: Windows 7, Grinder 3..4

Results we are seeing are showing that this is only partially fixed.
We are testing a server with it's timeout set to 30 seconds.

For 5 users we are see these results ( 3 time out almost immediately, 2 time out at 30+ seconds [as expected] )
Thread, Run, Test, Start time (ms since Epoch), Test time, Errors, HTTP response code, HTTP response length, HTTP response errors, Time to resolve host, Time to establish connection, Time to first byte
3, 0, 1, 1278003026863, 226, 0, 200, 0, 0, 1278003026881, 1278003026980, 214
2, 0, 1, 1278003026863, 228, 0, 200, 0, 0, 1278003026881, 1278003026980, 219
0, 0, 1, 1278003026863, 229, 0, 200, 0, 0, 1278003026881, 1278003026980, 220
4, 0, 1, 1278003026863, 31228, 0, 200, 1, 0, 1278003026881, 1278003026976, 31218
1, 0, 1, 1278003026863, 31229, 0, 200, 1, 0, 1278003026881, 1278003026979, 31219

I have attached the grinder.py files


----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2010-09-23 02:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 30 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Philip Aston (philipa)
Date: 2010-07-10 16:12

Message:
All of the requests appear to have returned successfully, with a response
code of 200. This can only happen if the request completes and the server
returns a response with a 200 status code. You will have to look to the
server as to why 3 of them returned quickly, and 2 of them waited until the
server time out of 30s was exceeded.

This has nothing to do with the grinder setTimeOut value, which I see you
are setting to 60s.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3023985&group_id=18598

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev