Thanks for the idea. I'll try the HttpClient sampler instead. "> Perhaps add "Connection close" to some of the samplers." Is it possible to do this with the sampler? How?
About the RAM, the peak memory of the java.exe process was ~450m and the Xmx flag was 640m, so, in this case all was ok from this point of view (I assume). On Thu, Jul 23, 2009 at 5:29 PM, sebb<[email protected]> wrote: > On 23/07/2009, Adrian Speteanu <[email protected]> wrote: >> It doesn't seem related to the server or the application tested. In >> the logs of JMeter nothing is written during the test (i found only >> start and stop threads). >> Any ideas on why it happens / how to avoid it? >> >> [ the error message ] >> " >> java.net.BindException: Address already in use: 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.SocksSocketImpl.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.<init>(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) >> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown >> Source) >> at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown >> Source) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java:490) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1037) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1023) >> at >> org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:346) >> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243) >> at java.lang.Thread.run(Unknown Source) >> " > > I suspect you may have run out of sockets. > > Perhaps add "Connection close" to some of the samplers. > > Try using the HttpClient sampler instead of the default HTTP sampler. > >> [test system] windows xp pro, 1g ram > > More RAM would be better. > >> jmeter 2.3.4 (i have modified the loggin level to >> info for most indicators) >> jvm 1.6.0_13 >> the test is very light for the server and response times are good; >> i have a bit to many listeners > > You can always reload the JTL file in a different Listener after the > test has completed. > >> - i am interested in comparing results >> for same action in various situations, however the virtual machine >> behaved ok, stayed well within the max heap memory and during the test >> the processor wasn't loaded more than 40-50% on average, so i hope >> that wouldn't be the problem, I suspect network issues. > > >> I am new to the JMeter Users List so I don't know if this was discussed >> before. > > That's what the mail archives are for ;-) > >> --------------------------------------------------------------------- >> 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]
