[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grinder-use
Subject:    Re: [Grinder-use] Premature EOF Exception
From:       Tuvell_Walter () emc ! com
Date:       2009-05-12 13:04:17
Message-ID: 0F3F903BA6B4A54984787888AF6EA5C402677C5F () CORPUSMX40A ! corp ! emc ! com
[Download RAW message or body]

Hey Roy, nice to meet you.

I remember that problem well.  In my case, Grinder was bombing out with
a Premature EOF, so there was initial suspicion Grinder itself was at
fault.  But upon closer analysis (Wireshark), it turned out the server
under test (our own web server) was the culprit.  It was illegally
closing the connection by "prematurely" sending a TCP FIN/ACK instead of
HTTP 200/OK as it should have.  [As noted in the post you cite, the
fault was actually due to a bug in a 3rd party library, Axis2c, which
has since been fixed.]  This sounds extremely similar to your
experience.  In particular, it sounds like the problem is on the
server-side (or maybe network, but I doubt that), not on the
Grinder-side.

What's different between our problems is that in my case the problem was
related to message size (the Premature EOF happened when response
message was > 173K approx), while your problem is related to number of
threads (which I presume means "number of simultaneous outstanding
requests to the server").

Interestingly, the post you cite was in response to another Grinder user
("aray") who was also seeing a number-of-threads Premature EOF.
Unfortunately, aray did not follow-up on the list with the conclusions
of his investigation.

Aray: If you are reading this, could you please let us know what you
found?

Roy: Are there any server settings for number of simultaneous clients?
Can you run with >10 threads using a different WS operation mix?  Can
you try hardware (maybe the ESX environment is somehow screwing up,
though hard to see why)?

Beyond this, I don't really have any further suggestions to give you,
other than ones you could figure out for yourself (since it looks like
you're trekking down the same paths I would try myself).  Sorry!


 

-----Original Message-----
From: RoyPorter [mailto:asp1@porter.me.uk] 
Sent: Tuesday, May 12, 2009 8:20 AM
To: grinder-use@lists.sourceforge.net
Subject: [Grinder-use] Premature EOF Exception


I've been having problems over the last few days with a Grinder script
that
keeps giving me Premature EOF Exceptions when I put the load up over 10
threads.

I'm using Grinder version 3.2, I've tried running against different
servers,
different Java web server installations (Jboss and Jetty), and using a
linux
client machine, as well as windows. All give the same results. The only
common thing about the servers is that they are virtual machines running
on
VMWare ESX3. (different physical hosts).

I've searched through the mailing lists for past problems of this type
and
I've gone to the extent of putting a network analyzer on to try and
diagnose
the problem. (In the process changing the exception message so that it
output the source port to aid tracking down the packets to inspect). 

It looks like the behaviour I'm seeing is as Walt describes in this
thread:
http://www.nabble.com/For-threads->-than-20,-HTTPClient.RetryException:-
Premature-EOF-encountered-tt22120442.html#a22162863,
i.e. the server is sending a TCP FIN/ACK to close the connection. 

My question is, where do I go from here to carry on with this diagnosis?



-- 
View this message in context:
http://www.nabble.com/Premature-EOF-Exception-tp23500769p23500769.html
Sent from the Grinder - User mailing list archive at Nabble.com.


------------------------------------------------------------------------
------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use
[prev in list] [next in list] [prev in thread] [next in thread]