Connection timed out: connect

MichaelT_
MichaelT_ used Ask the Experts™
on
Hello,

I am currently running some performance tests using WebLogic 10.3.2 as the application server on Solaris SPARC 10, the tests consist of sending and receiving SOAP requests and measuring being run using "The Grinder".  

Now at higher loads I am starting to see a number of "Connection timed out: connect" errors in my logs, I am just wondering if anyone has ideas on settings which may help decrease these errors

- TCP on Solaris?
- Threads in WebLogic (which are self-tuning)?
- Something else?

I have included the whole error message below too.
java.net.ConnectException: Connection timed out: 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 java.net.Socket.<init>(Unknown Source)
	at java.net.Socket.<init>(Unknown Source)
	at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3389)
	at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3082)
	at HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2876)
	at HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2668)
	at HTTPClient.HTTPConnection.Post(HTTPConnection.java:1170)
	at net.grinder.plugin.http.HTTPRequest$7.doRequest(HTTPRequest.java:864)
	at net.grinder.plugin.http.HTTPRequest$AbstractRequest.getHTTPResponse(HTTPRequest.java:1208)
	at net.grinder.plugin.http.HTTPRequest.POST(HTTPRequest.java:859)
	at net.grinder.plugin.http.HTTPRequest.POST(HTTPRequest.java:755)
	at net.grinder.plugin.http.HTTPRequest.POST(HTTPRequest.java:738)
	at sun.reflect.GeneratedMethodAccessor1711.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.python.core.PyReflectedFunction.__call__(Unknown Source)
	at org.python.core.PyMethod.__call__(Unknown Source)
	at org.python.core.PyObject.__call__(Unknown Source)
	at org.python.core.PyInstance.invoke(Unknown Source)
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentedPyJavaInstanceForJavaInstances.access$001(InstrumentedPyJavaInstanceForJavaInstances.java:44)
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentedPyJavaInstanceForJavaInstances$1.call(InstrumentedPyJavaInstanceForJavaInstances.java:61)
	at net.grinder.engine.process.instrumenter.traditionaljython.PyDispatcher.dispatch(PyDispatcher.java:70)
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentationHelper.dispatch(InstrumentationHelper.java:102)
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentedPyJavaInstanceForJavaInstances.invoke(InstrumentedPyJavaInstanceForJavaInstances.java:58)
	at org.python.pycode._pyx0.__call__$2(C:\grinder\scripts\FS.py:103)
	at org.python.pycode._pyx0.call_function(C:\grinder\scripts\FS.py)
	at org.python.core.PyTableCode.call(Unknown Source)
	at org.python.core.PyTableCode.call(Unknown Source)
	at org.python.core.PyTableCode.call(Unknown Source)
	at org.python.core.PyFunction.__call__(Unknown Source)
	at org.python.core.PyMethod.__call__(Unknown Source)
	at org.python.core.PyObject.invoke(Unknown Source)
	at org.python.core.PyInstance.__call__(Unknown Source)
	at org.python.core.PyObject.__call__(Unknown Source)
	at net.grinder.engine.process.jython.JythonScriptEngine$JythonWorkerRunnable.run(JythonScriptEngine.java:193)
	at net.grinder.engine.process.GrinderThread.run(GrinderThread.java:131)
	at java.lang.Thread.run(Unknown Source)

Open in new window

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
Thanks heaps, looks to be improved through adjusting the tcp settings in solaris with the following:

ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 4096

Thanks again :)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial