I think I might have found it. Based on your suggestion that it is the OS/JVM that is causing the timeout, I found this article:
http://www.sekuda.com/overriding_the_default_linux_kernel_20_second_tcp_socket_connect_timeout I tried an increase in the tcp_syn_retries setting and that did seem to reduce the number of connection errors that I am seeing. I just need to find the value that works correctly for me. On Tue, 2014-09-09 at 14:49 +0100, sebb wrote: > On 9 September 2014 14:24, Brian Devaney <[email protected]> wrote: > > > The full exception is: > > > > java.net.ConnectException: Connection timed out > > at java.net.PlainSocketImpl.socketConnect(Native Method) > > at > > java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > > at > > java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > > at > > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > > at java.net.Socket.connect(Socket.java:579) > > at java.net.Socket.connect(Socket.java:528) > > at java.net.Socket.<init>(Socket.java:425) > > at java.net.Socket.<init>(Socket.java:280) > > at > > org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80) > > at > > org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122) > > at > > org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > > at > > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > > at > > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > > at > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > > at > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) > > at > > org.apache.jmeter.protocol.http.sampler.SoapSampler.sample(SoapSampler.java:272) > > at > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1105) > > at > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1094) > > at > > org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:429) > > at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:257) > > at java.lang.Thread.run(Thread.java:722) > > > > > That is timing out on the connect, which I think may well have an OS upper > limit. > > But in any case, it is not getting as far as starting to process the > request. > > On Tue, 2014-09-09 at 14:20 +0100, sebb wrote: > > > > On 9 September 2014 14:10, Brian Devaney <[email protected]> wrote: > > > I have a series of test scripts where the only error that I am getting > > > is a ConnectException Connection Timed Out error every so often. I want > > > to find out how long the worst of these calls take, so I do not want to > > > see a connection timeout, but have that connection finish whatever it > > > was doing and record how long it took. > > > > > > In order to remove the timeout, I have gone through the documentation > > > and found the entry in jmeter.properties and set > > > > > > http.timeout=0 > > > httpclient.parameters.file=http.parameters > > > > > > and added an entry in http.parameters to > > > > > > http.connection.timeout$Integer=0 > > > > > > This should have taken care of the possibility for timeouts in my test, > > > but I still see a number of them. Is there anything I am missing? The > > > calls that are timing out are SOAP/XML-RPC calls. Thank you for your > > > help. > > > > It's possible that the OS/JVM is implementing the timeout. > > > > Without a bit more detail it's difficult to know. > > > > > -- > > > Brian Devaney > > > Software Developer > > > DocFinity® > > > (814) 238-0038x274 > > > mailto:[email protected] <[email protected]> > > > http://www.docfinity.com/ > > > > > > > > > > > > DISCLAIMER: This email may contain proprietary information, some or all > > > of which may be legally privileged. It is for the intended recipient > > > only. If an addressing or transmission error has misdirected this email, > > > please notify the author by replying to this email. If you are not the > > > intended recipient, you may not use, disclose, distribute, copy, print, > > > or rely on this email. > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > -- > > > > Brian DevaneySoftware DeveloperDocFinity®(814) > > 238-0038x274mailto:[email protected]://www.docfinity.com/ > > > > > > DISCLAIMER: This email may contain proprietary information, some or all > > of which may be legally privileged. It is for the intended recipient > > only. If an addressing or transmission error has misdirected this email, > > please notify the author by replying to this email. If you are not the > > intended recipient, you may not use, disclose, distribute, copy, print, > > or rely on this email. > > > > > > -- Brian Devaney Software Developer DocFinity® (814) 238-0038x274 mailto:[email protected] http://www.docfinity.com/ DISCLAIMER: This email may contain proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you may not use, disclose, distribute, copy, print, or rely on this email. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
