jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bo Bodnar" <>
Subject Re: Problem with connection timeout during tests.
Date Tue, 06 Nov 2018 15:58:50 GMT

Do you have the problems if only case (1) is running?  case(2) is running?
cases (1) and (2) are running?  If you've problems with case (2) only, then
you may have hardware issues (defective connections, defective
router/switch, etc.).  What is the link capacity between the load generator
and your target?

I'd put something like Wireshark (t-shark would probably be better) on the
load generator and your target and see what both are seeing at the same
time traffic is being generated.  This means both are time-synchronized.  I
don't know if Windows 10 is running NTP; if not, you'll have to mess with
the registry to have everything running off of a common NTP server and make
sure the synchronization is done frequently.

   Bohdan L. Bodnar                                                                  
   Lead Performance Engineer                                                         
   E-mail:                               222 South Riverside Plaza 
                                                                    Chicago, IL 60606 
                                                                        United States 

From:	Mariusz W <>
To:	JMeter Users List <>
Date:	11/06/2018 09:33 AM
Subject:	Re: Problem with connection timeout during tests.

Maybe you don't have working routing to server...


On Tue, Nov 6, 2018 at 3:36 PM Janusz Michalski <>

> Hi,
> I'm runnig Jmeter tests on following environment:
> - Windows 10 Pro x64, 16 GB RAM, i5-6200 2.3GHz (2 cores), SSD
> 4 test cases at once:
> 1) First with 90 http Gets per 10 seconds
> 2) Second with 10 http Posts per 10 seconds
> 3) Third with 3 http Gets per 10 seconds
> 4) Fourth with 1 http Put per 60 seconds
> For a total of ~104 http requests per 10 seconds
> And I'm getting following error for most of requests:
> org.apache.http.conn.HttpHostConnectException: Connect to
> [/] failed: Connection timed out: connect
> Caused by: Connection timed out: connect
> Please, advise me what can be the issue, possible solution or if you need
> more data for investigation.
> Janusz Michalski
> Senior QA Automation Engineer
> Please consider the environment before printing this e-mail.
> ________________________________
> This e-mail (including any attachments) is intended solely for the use of
> the individual or entity to which it is addressed and may contain
> confidential information. This message is not a binding agreement and
> not conclude an agreement without the express confirmation of the
> superior or a director of the company.
> If you are not the intended recipient, you should immediately notify the
> sender and delete the message along all the attachments. Any disclosure,
> copying, distribution or any other action is prohibited and may be
> No e-mail transmission can be guaranteed to be 100% secure or error-free,
> as information could be intercepted, corrupted, lost, destroyed, arrive
> late or incomplete, or contain viruses. Although SpyroSoft has taken
> precautions to ensure that this e-mail is free from viruses, the company
> does not accept liability for any errors or omissions in the content of
> this message, which arise as a result of the e-mail transmission. This
> e-mail is deemed to be professional in nature. SpyroSoft does not permit
> the employees to send emails which contravene provisions of the law.

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