Connection timed out: connect


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. Connection timed out: connect
	at Method)
	at Source)
	at Source)
	at Source)
	at Source)
	at Source)
	at Source)
	at<init>(Unknown Source)
	at<init>(Unknown Source)
	at HTTPClient.HTTPConnection.getSocket(
	at HTTPClient.HTTPConnection.sendRequest(
	at HTTPClient.HTTPConnection.handleRequest(
	at HTTPClient.HTTPConnection.setupRequest(
	at HTTPClient.HTTPConnection.Post(
	at net.grinder.plugin.http.HTTPRequest$7.doRequest(
	at net.grinder.plugin.http.HTTPRequest$AbstractRequest.getHTTPResponse(
	at net.grinder.plugin.http.HTTPRequest.POST(
	at net.grinder.plugin.http.HTTPRequest.POST(
	at net.grinder.plugin.http.HTTPRequest.POST(
	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(
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentedPyJavaInstanceForJavaInstances$
	at net.grinder.engine.process.instrumenter.traditionaljython.PyDispatcher.dispatch(
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentationHelper.dispatch(
	at net.grinder.engine.process.instrumenter.traditionaljython.InstrumentedPyJavaInstanceForJavaInstances.invoke(
	at org.python.pycode._pyx0.__call__$2(C:\grinder\scripts\
	at org.python.pycode._pyx0.call_function(C:\grinder\scripts\
	at Source)
	at Source)
	at 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$
	at Source)

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelT_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 :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.