I can second that.

Cheers Oliver 

-----Original Message-----
From: Richa Pant [mailto:[EMAIL PROTECTED] 
Sent: Monday, 22 May 2006 14:05
To: JMeter Users List
Subject: Re: Getting Exception "java.io.IOException: Stream closed"

Hi,
   
  I did observe TimeOut exceptions, apart from  'java.io.IOException: Stream 
closed exception'. Jmeter log was also showing 'Connection Timed Out'.
  
Following is the exception,
  > java.net.ConnectException: Connection timed out: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method) at 
> java.net.PlainSocketImpl.doConnect(Unknown Source) at 
> java.net.PlainSocketImpl.connectToAddress(Unknown Source) at 
> java.net.PlainSocketImpl.connect(Unknown Source) at 
> java.net.Socket.connect(Unknown Source) at 
> java.net.Socket.connect(Unknown Source) at 
> sun.net.NetworkClient.doConnect(Unknown Source) at 
> sun.net.www.http.HttpClient.openServer(Unknown Source) at 
> sun.net.www.http.HttpClient.openServer(Unknown Source) at 
> sun.net.www.http.HttpClient.(Unknown Source) at 
> sun.net.www.http.HttpClient.New(Unknown Source) at 
> sun.net.www.http.HttpClient.New(Unknown Source) at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)...
>

   
  Since today I was facing the ' java.io.IOException: Stream closed' exception 
even with 5 threads, I reduced the test case to 3 threads. I observed the 
following results.
   
  On Running two test cases of 3 threads each , using separate Jmeter 
instances,simultaneously from a single machine using 70Kbps connection - Some 
requests are failing with exception ' java.io.IOException: Stream closed'.
   
  On Running two test cases of 3 threads each ,simultaneously from different 
machines using 70Kbps connections - All requests are passing.
   
  Also, even if the requests are failing in Jmeter, I did'nt observe any Error  
in WebServer logs.
Hope the findings will be of some help,
  
Regards,
  Richa

sebb <[EMAIL PROTECTED]> wrote:
  As I understand it:
* this is happening with both HTTP Samplers. These use different 
implementations.
* neither is reporting timeout errors, which I believe they would do - if they 
occurred.

It does not look like timeouts to me, nor does it look like a problem in JMeter.
But I could be wrong, as I don't have first-hand experience of the problem.

S.
On 22/05/06, Oliver Erlewein (DSLWN) wrote:
> Hi
>
> I see this happening too. My hunch is, that it is a timeout problem of 
> jmeter/java with the HTTP Client. Sebb I think I did send you that 
> data on what I had found. We'll be researching this in more depth in a 
> couple of days. I'll get back to this discussion then.
>
> Cheers Oliver
>
> -----Original Message-----
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: Monday, 22 May 2006 11:37
> To: JMeter Users List
> Subject: Re: Getting Exception "java.io.IOException: Stream closed"
>
> Agreed, it would not be practical to run 100 instances - but it would 
> be useful to find out if you can get past 5 simultaneous threads.
>
> The behaviour with 10, 15, 20 threads etc might give a better idea as 
> to why the problems are occurring.
>
> The size in the View Results in Table is the Response size, not the 
> Request size.
>
> S.
> On 21/05/06, Richa Pant wrote:
> > Hi,
> >
> > Thanks Sebb. I ll try dividing the threads into group of 5 and
> running from separate Jmeter instances.
> > But think this ll be a very hard thing to do if I want to try 500
> simultaneous hits.
> > One thing more I observed when I looked at the results in "View
> Results in Table".
> > All the Requests with Bytes as 512 are passing and any requests
> having Bytes greater than 512(e.g 735,1185, 1147....etc) are failing.
> >
> > I checked yesterdays WebServer Logs also.Thats seems to be clear.
> >
> > Also I was wondering why the Sampler Requests size is being shown as
> 512 .. bytes in "View Results in Table", when the files that are 
> posted in Sampler Requests are of same size(50KB). It seems that 
> Jmeter is dividing the data into chunks before sending. But when I see 
> the #Samplers in aggregate report its correctly = (no.of threads) * 
> (No.of Requets per thread).
> > It seems Jmeter is sending the correct no of requests but the size
> of the Requests shown in "View Results in Table" are different from 
> the file size posted with the Request.
> >
> > Thanks alot for all the help,
> >
> > Regards,
> > Richa
> >
> > sebb wrote:
> > This also looks like something external to JMeter.
> >
> > I'm not familiar with the details of HTTPClient, but the method name
> > readStatusLine() suggests that the data has been successfully 
> > uploaded, and that JMeter is waiting for the remote server to respond.
> >
> > All I can suggest now is that you run several instance of JMeter, 
> > each
>
> > with 5 threads - because you know that JMeter and the server can 
> > cope with 5 threads.
> >
> > If the problems continue, then this seems to me that the problem 
> > lies with the server - or perhaps the network. It might be worth 
> > trying to run JMeter from more than 1 system.
> >
> > S.
> [...]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



                
---------------------------------
Blab-away for as little as 1ยข/min. Make  PC-to-Phone Calls using Yahoo! 
Messenger with Voice.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to