Bug 60676 - Suspicion of an issue with load testing HTTPS related to Keep-Alive
Summary: Suspicion of an issue with load testing HTTPS related to Keep-Alive
Status: RESOLVED WORKSFORME
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 3.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on: 60689 60690
Blocks:
  Show dependency tree
 
Reported: 2017-02-01 21:02 UTC by Philippe Mouawad
Modified: 2017-02-04 15:07 UTC (History)
1 user (show)



Attachments
Test plan (11.68 KB, application/xml)
2017-02-01 21:02 UTC, Philippe Mouawad
Details
2.13 memory behaviour (354.16 KB, image/png)
2017-02-01 21:06 UTC, Philippe Mouawad
Details
Nightly build (3.2) heap behaviour with httpclient4.time_to_live=0 and httpclient4.validate_after_inactivity=0 (286.62 KB, image/png)
2017-02-01 21:07 UTC, Philippe Mouawad
Details
Heap Memory 3.2 default (377.40 KB, image/png)
2017-02-01 21:08 UTC, Philippe Mouawad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2017-02-01 21:02:58 UTC
Created attachment 34703 [details]
Test plan

Following this thread:
http://mail-archives.apache.org/mod_mbox/jmeter-user/201702.mbox/%3CCABrgpQdsjHmkT90BqzJHZHzTHzrx3zeLu%2BPA0RN%3D%3DwhzM6bO8Q%40mail.gmail.com%3E

I create this bugzilla for investigation.

I attach here a simplified test based on what user provided but not using any 3rd party plugin:

- https://jmeter-plugins.org/wiki/VariablesFromCSV/
- https://jmeter-plugins.org/wiki/ConcurrencyThreadGroup/
Comment 1 Philippe Mouawad 2017-02-01 21:06:39 UTC
Created attachment 34704 [details]
2.13 memory behaviour
Comment 2 Philippe Mouawad 2017-02-01 21:07:33 UTC
Created attachment 34705 [details]
Nightly build (3.2) heap behaviour with httpclient4.time_to_live=0 and httpclient4.validate_after_inactivity=0
Comment 3 Philippe Mouawad 2017-02-01 21:08:12 UTC
Created attachment 34706 [details]
Heap Memory 3.2 default
Comment 4 Philippe Mouawad 2017-02-04 15:07:03 UTC
Issue was due to using default settings of JMeter 3.1 which are not suited for the machine, network and use case.

Increasing lifetime of httpclient4.time_to_live fixed the problem for user.
Within this bugzilla 2 bugs were detected and fixed:
- Bug 60689
- Bug 60690