hi ok, I assume you've tried out the other things recommended by sebb (and i think emailed by adrian). Do you get any errors on tomcat when you start getting this error on the JMeter client
Can you monitor the sockets on both client and server ? are there too many open sockets with TIME_WAIT ? There was some tuning parameter related to the time that you close the socket and the time that the system actually closes which used to affect the server . Googling I found this http://publib.boulder.ibm.com/infocenter/cmgmt/v8r3m0/index.jsp?topic=/com.ibm.eclient.doc/trs40019.htm Adrian Ive never seen this happen on light loads. And Im sure this problem wouldve been reported more often on light loads in jmeter. in which case this seems to be OS/machine specific problem? regards deepak On Wed, Jul 29, 2009 at 11:40 PM, shaoxianyang <[email protected]> wrote: > > I then lower the load to 200(threads)x200(loops), no error happens. > > Then I change the setup to be 200(threads)x400(loops). The only error is > BindException (Address already in use). I don't see any connection refused > exception. > > Therefore, we still don't know what cause for BindException. The log shows > some BindException takes long to happen, such as 3071(ms). From how long > it > takes, it is more of exception that server throw, instead of client side > socket problem. > > Can anyone make comment on this? At least that BindException. Now I am > totally confused. Changing to another host does not eliminate this > problem. > > Thanks. > > > > Shaoxian > -- > View this message in context: > http://www.nabble.com/java.net.BindException-returned-from-http-sampler-tp24716020p24732916.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
