Hi ConnectionRefused might be because you have overloaded the webserver (most have a tcp/http backlog after which they will refuse connections- Im not sure where this setting is for tomcat). It might also happen because of ulimit (on unix) I'd take this as a sign that you are running too high a load. You have to reduce the load or tune tomcat(or run a cluster of webservers) . It might also indicate that your OS is not tuned too well. >For the original BindException, I don't know if program loops more, will that come back again? I would hope not. Let us know :)
>Is there any way in jmeter to discard those error case, and only let the aggregate statistic focus on the working ones, so that I get a good idea about the response time? write your own custom XSLT or SAX filter to filter out the results you dont want from the jtl is the only way i know regards deepak On Wed, Jul 29, 2009 at 2:22 PM, shaoxianyang <ysxsu...@hotmail.com> wrote: > > Yeh, I did try with another machine. Running 1000 threads and each loop > 100 > times. > > Although I don't see the bindException, but I still see 10% of Connection > RefusedException. I am still not sure why Connection RefusedException, > instead of Connection TimeoutException. > > For the original BindException, I don't know if program loops more, will > that come back again? > > Is there any way in jmeter to discard those error case, and only let the > aggregate statistic focus on the working ones, so that I get a good idea > about the response time? > -- > View this message in context: > http://www.nabble.com/java.net.BindException-returned-from-http-sampler-tp24716020p24727856.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >