On 23/09/06, Parham, Clinton <[EMAIL PROTECTED]> wrote:
Hello,I'm using JMeter 2.2 to perform load testing against a web application running on Tomcat 5.5.16 on a Windows 2003 server. When I simulate 200 users all is well. When I jump up to about 300, I start seeing SocketExceptions in JMeter as shown below - somewhere between 5% and 10% of the requests fail this way. CPU utilization on the client and server are fairly high during the test but not constantly above 90%. I don't see any errors in the Tomcat logs (with default/standard logging). I believe Tomcat is using tcnative-1.dll and the SSL connector parameters shown below. Has anyone seen this behavior before or know what I need to do to avoid/troubleshoot the errors? Thank you, Umk <Connector port="443" maxHttpHeaderSize="8192" maxThreads="500" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="150" scheme="https" secure="true" SSLEngine="on" SSLCertificateFile="${catalina.home}/ssl/test.cer" SSLCertificateKeyFile="${catalina.home}/ssl/test.key" /> Complete stack trace seen within JMeter: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at
The client received an error from the server.
com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275) at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275) at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(DashoA12275) at com.sun.net.ssl.internal.ssl.SunJSSE_ax.i(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.k(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA12275)
Looks like the client is trying to initialise the SSL connection
at sun.net.www.protocol.https.HttpsClient.afterConnect(DashoA12275) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Da shoA12275) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl.co nnect(DashoA12275) at org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.j ava:406) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:658) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:647) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247) at java.lang.Thread.run(Thread.java:534)
Googling found this: http://forum.java.sun.com/thread.jspa?threadID=294609&start=0 Reply 7 refers to the a situation when this might happen at the end of a session, but this does not seem to be the case here, judging by the names of the methods in the stack trace. All I can suggest is to try running JMeter on two clients to generate the same load, and see if you get the same problem. If so, then it is unlikely to be a JMeter problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
