Re: Premature EOF encountered bug

Steven,

The stack traces in your attachment indicate a "Premature EOF" during a 
different part of the HTTP protocol to your original report. 
Consequently, the diagnostic patch does not add any useful information.

However, together with the low level of similar reports, this second 
symptom makes me confident that the problem is not due to a bug in the 
HTTPClient library used by The Grinder. Rather, there is something 
"upstream" from The Grinder that is occasionally terminating HTTP 
connections. This might be anything, e.g. the server process, something 
in the network, the client or server O/S, firewall, ...

Interestingly, HTTP allows for two different ways to specify the number 
of bytes in a response body. The first is for the server to provide the 
length up-front in the response header. This was happening in your 
original scenario, and the error was occurring because the server said 
it was going to deliver X bytes, but the connection was closed before 
The Grinder had received that many. To support scenarios where the 
server doesn't know how many bytes its going to send (useful because it 
avoids the need to buffer large responses, for example) HTTP 1.1 added 
another way: "chunked transfer". In this case, the response is made up 
of several parts, with the server saying "Here's a chunk of X bytes, 
[data follows], here's a chunk of Y bytes, [data], ..., we're done". In 
your second scenario, the connection is closed when The Grinder is 
expecting a new chunk.

I know this doesn't help too much with your testing.

I'll add this discussion, and your attachment to the bug. Please 
continue discussion there. (To add an attachment, first log in, then use 
the "Add a file" link. Its a little hard to see, but its there).

- Phil




On 30/05/11 18:32, Steven Swart wrote:
> Hi Philip!
>
> With reference to the following bug:
>
> https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3202566&group_id=18598
>
> I have encountered a similar problem on my test run
> today. I was running one agent with a hundred worker
> threads against my application. I hit the 'Premature
> EOF encountered' error again. My test did not complete,
> I aborted it as soon as I encountered the errors. Please
> see attached file for details. It contains the std err output
> from that patch you uploaded, my Grinder test script,
> and the complete output logs etc from my agent.
>
> Here is the id string for my webserver:
>
> Apache/2.0.63 (Unix) DAV/2 mod_perl/2.0.0 Perl/v5.8.4 Server at
> www.test.lan Port 80
>
> We are also using FastCGI.
>
> Sorry for posting this here, but I was unable to figure
> out how to upload an attachment to this bug.
>
> I hope this helps...
>
> Regards,
> S.
>
>
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
>
>
> _______________________________________________
> Grinder-development mailing list
> Grinder-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/grinder-development

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2

_______________________________________________
Grinder-development mailing list
Grinder-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/grinder-development