[ grinder-Bugs-3202566 ] Premature EOF encountered

Bugs item #3202566, was opened at 2011-03-08 04:31
Message generated for change (Comment added) made by philipa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3202566&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: James Farrier (jamesfarrier)
Assigned to: Philip Aston (philipa)
Summary: Premature EOF encountered

Initial Comment:
I realize there are atleast two other of these issues detailed here.  My one however follows a different parttern.  I don't receive the following:HTTPClient.StreamDemultiplexor.retry_requests(StreamDemultiplexor.java:5 
26) 

Instead my stack trace looks like this:
8/03/11 3:03:29 AM (thread 6 run 0 test 302): Aborted run due to Java exception calling TestRunner
Java exception calling TestRunner
	File "C:\grinder\.\WorkbookS2.py", line 477, in page3
	File "C:\grinder\.\WorkbookS2.py", line 894, in __call__
	File "c:\grinder\grinder.py", line 27, in __call__
Caused by: java.io.EOFException: Premature EOF encountered
	at HTTPClient.StreamDemultiplexor.read(StreamDemultiplexor.java:300)
	at HTTPClient.RespInputStream.read(RespInputStream.java:155)
	at HTTPClient.HTTPResponse.readResponseData(HTTPResponse.java:1011)
	at HTTPClient.HTTPResponse.getData(HTTPResponse.java:515)

Does anyone know what might have cause this exception to be thrown?

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

>Comment By: Philip Aston (philipa)
Date: 2011-03-21 21:17

Message:
Patch attached - please use it to diagnose in conjunction with an HTTP
trace (perhaps taken using the tcpproxy) to determine whether the server is
sending the correct content length.

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

Comment By: Philip Aston (philipa)
Date: 2011-03-21 19:33

Message:
This code path occurs if the server has returned a response with a
Content-Length header, and then proceeded to close the response stream
before fully transmitting a body of the specified number of bytes.

I suspect that this is a server issue, rather than a problem with The
Grinder or the HTTPClient library. I'll produce a debug patch to allow us
to diagnose this a little further.

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

Comment By: Philip Aston (philipa)
Date: 2011-03-21 19:29

Message:
Bug 3206627 has duplicate symptoms.

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

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

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar