What os are you using to run JMeter? I see this problem in gui and non gui mode using JMeter in a windows environment. I have not tried it in a xnix environment. I suspect the problem is caused by loosing either fin packets them selves or the kernel is not registering that they have occured or not passing on the close message to winsoc. Maybe you could try running the test, weight till you believe it has hanged and then run Netstat to see what sockets are open. You may be able to see what is going off and track any open connections. Let me know if you find out anything that lines up with what I am saying, or if there is a totally different explanation. Cheers AJ Dr Alexander J Turner Project Network +44 (0) 7917 065072 Con Call: 0870 241 3425/3342654#
________________________________ From: Vladimir Tsygankov [mailto:[EMAIL PROTECTED] Sent: Fri 06/10/2006 18:43 To: 'JMeter Users List' Subject: TPN POSSIBLE SPAM:Problem with many thread groups in Non GUI mode Problem with many thread groups in Non GUI mode. We have a test plan with 50 threads in Thread Group. Every thread group is modelling a separate user. When we run the test in Non GUI mode some threads stop running in arbitrary moment of time. We tried to increase Ramp-up time and delay between requests but it didn't help. We looked though the assertion logs and saw that for some threads requests are not sent from some time point. Notes. 1. CPU was busy in about 100% during testing. 2. For 2-20 thread groups the test worked fine. For GUI mode (50 threads) it works fine. 3. We are using the next parameters for Non GUI JMeter mode: java -Xincgc -jar ApacheJMeter.jar -n -t <...> Can anybody help us? Thanks in advance, Vladimir. --------------------------------------------------------------------- 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]
