Guys, As I mentioned before, I've reproduced this problem with only 10 threads, testing a server that wasn't on the local machine and was not being used for anything else than the test.
Therefore, we can eliminate the fact that it takes only high loads to reproduce the issue. I test with jmeter 2.3.4 and the server is also a tomcat. I have a windows vista and the application server OS is a linux (has a database server as well). It's pretty well tuned, both it and the OS (I am confident in the net admin that takes care of the servers). sebb replied to me in the other thread about this issue: " Perhaps add "Connection close" to some of the samplers. Try using the HttpClient sampler instead of the default HTTP sampler. " He suggested unchecking the Keep-Alive option from the sampler. I assume from this and all that you have discussed that, for some reason, JMeter doesn't closes its connection to the server properly. Possible causes: 1. bug (i think it would have been encountered by several other persons) 2. the way the test is configured and some weird scenarios that we encountered 3. network card problems (including deprecated drivers). I had the one from the test machine replaced to see if there are improvements. I have also encountered the Connection refused issue, but didn't thought to investigate further, I just lowered the test threads to a point where it didn't occur any more, however the bindException still appears, and pretty often. To disregard this error, in Summarizer, check the Successes checkbox, to record only good samples. In my case this is the only exception occurring, so had to use this workaround to get quick results. On Thu, Jul 30, 2009 at 9:51 AM, Milamber<[email protected]> wrote: > Hello, > > What is the operating system of the server? and Jmeter? > > During the test, there is possible to execute a "netstat -an" and calcule > the number of connections between the server and the Jmeter (example: > "netstat -an | grep 8080 | wc -l" if Tomcat's port is 8080) > > If server is Unix or Linux, what is the result of command "ulimit -n"? > (default in Linux is 1024 for the number of max open files, which would > explain the problem BindEx at 1000 ...) > > Bye, > Milamber > > > Le 30/07/2009 07:19, shaoxianyang a ecrit : >> >> Hi deepak, >> >> even after I move my jmeter process to another machine. I still get the >> mix >> of BindException and Connection Refused. >> >> I set the Tomcat server to take 300 connections concurrently at any given >> time. I lower my load to 200, and loop (go up to) 2000. >> Now I am not convinced why I still see the BindException. This time, what >> address can be the same? >> >> I can accept the Connection Refused error, although Tomcat is more than >> cable of handling it (300 threads in pool to handle 200 request at any >> given >> time). >> Shaoxian >> > > > --------------------------------------------------------------------- > 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]
