jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Richard <>
Subject Connection Timed out - Jmeter 2.4
Date Mon, 11 Aug 2014 13:33:06 GMT

I've run into an issue that I'm not really sure how to troubleshoot anymore
and any new ideas would be appreciated.

I am using Jmeter 2.4 . I'm not sure I am at liberty to send my .jmx script
along as it might be too much public information so I'll just try to
explain the issue.

I have this test that I'll run for performance testing of our website that
will have users log in, submit some forms and then log out.

Our servers are Red Hat 5 for the web servers and Jmeter runs on Red Hat 6.
All traffic is kept internal to the network where the website servers are

This test has always worked fine up until recently. Now, if I go through
SSL, I get the following:

Response code: Non HTTP response code:
Response message: Non HTTP response message: SSL peer shut down incorrectly SSL peer shut down incorrectly

If I go through regular port 80, I get the following: Connection Timed out.

This will only happen to about < 2% of requests and the type of request is
varied: image, .htm file that calls some Java Spring logic, etc.

I thought this might be due to me re-arranging our Apache configuration but
I tried reverting to prior settings and this still happens.

It feels like some kind of server, network issue but I'm not sure how to
troubleshoot it further at this point.

I have tried to simplify the test by eliminating the log in process and
just hitting the log in form and that is fine. I then reduced the test to
logging in, just submitting one form and logging out and this has the same
socket issues.

Any suggestions on how to troubleshoot this further?

Our servers are with a hosted company and I've submitted a ticket to them.
They told me to check somaxconn I believe it was but this did nothing.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message