You are very welcome! One pitfall of using Wireshark, and why I think
t-shark may be better: if used for a long time, it will lock up. This is
because of the GUI. t-shark is Wireshark without the GUI. Make sure
everything's time synchronized; otherwise you won't be able to track
stimulus/response.
As others have pointed out: you may be overloading your target.
If you're conducting performance testing, you must know what the
performance requirements are (e.g., 90% latency under conditions XYZ shall
not exceed ABC milliseconds). If you're interested only in probing
performance operation, then there are no requirements as you're doing an
experiment.
Best regards,
Bo
Bohdan L. Bodnar
Lead Performance Engineer
1-312-871-5163
E-mail: [email protected] 222 South Riverside
Plaza
Chicago, IL
60606
United
States
From: Janusz Michalski <[email protected]>
To: JMeter Users List <[email protected]>
Date: 11/06/2018 10:14 AM
Subject: RE: Problem with connection timeout during tests.
Hi Bohdan,
Thanks for the advice, we will use Wireshark to investigate the traffic
between machines. I will keep you posted.
From: Bo Bodnar <[email protected]>
Sent: Tuesday, November 6, 2018 4:59 PM
To: JMeter Users List <[email protected]>
Subject: Re: Problem with connection timeout during tests.
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
1-312-871-5163
________________________________
E-mail: [email protected]<mailto:[email protected]>
222 South Riverside Plaza
Chicago, IL 60606
United States
[Inactive hide details for Mariusz W ---11/06/2018 09:33:02 AM---Hi, Maybe
you don't have working routing to server...]Mariusz W ---11/06/2018
09:33:02 AM---Hi, Maybe you don't have working routing to server...
From: Mariusz W <[email protected]<mailto:[email protected]>>
To: JMeter Users List <[email protected]<mailto:[email protected]
>>
Date: 11/06/2018 09:33 AM
Subject: Re: Problem with connection timeout during tests.
________________________________
Hi,
Maybe you don't have working routing to server...
Mariusz
On Tue, Nov 6, 2018 at 3:36 PM Janusz Michalski <[email protected]<
mailto:[email protected]>>
wrote:
> 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
> 10.98.40.106:6002 [/10.98.40.106] failed: Connection timed out: connect
> Caused by: java.net.ConnectException: 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 does
not conclude an agreement without the express confirmation of the sender's
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 illegal.
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.
