You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2019/07/02 03:33:58 UTC
[Bug 63535] New: More than 50000 connects were created when I run
test with 100 threads
https://bz.apache.org/bugzilla/show_bug.cgi?id=63535
Bug ID: 63535
Summary: More than 50000 connects were created when I run test
with 100 threads
Product: JMeter
Version: 5.1.1
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: 15527206908@163.com
Target Milestone: JMETER_5.2
More than 50000 connects were created when I run test with 100 threads, and it
used up all ports of my machine. However, only 200 connects were created when
using jmeter 3.2.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63535] More than 50000 connects were created when I run test
with 100 threads
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63535
aliyabo <15...@163.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #2 from aliyabo <15...@163.com> ---
I have a script with 100 threads which upon executing for 1 minute with
keep-alive enabled for all requests, and following are my observations:
1. httpclient.reset_state_on_thread_group_iteration=true
More than 50000 connects were created, and it used up all ports of my
machine. Do you have any idea to avoid it? With the default value 'true', What
considerations are based on?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63535] More than 50000 connects were created when I run test
with 100 threads
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63535
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
OS| |All
--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
This report lacks a lot of information and can't be solved without more
details:
* Please supply a simple test plan that we can run to reproduce the issue.
* Give more information on the used elements and the kind of server you are
talking to
* Which version of JMeter, Java, OS, ... are involved
Apart from this, it is always a good idea to use the mailing list first, in
case this is a known issue or something easily avoidable.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63535] More than 50000 connects were created when I run test
with 100 threads
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63535
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
By default:
httpclient.reset_state_on_thread_group_iteration=true
Which means a thread iteration correspond to a new user which is why SSL state
is reset for example.
In upcoming version of JMeter, you'll have more control in a clearer way on
this , have a look at:
- Bug 62861
You can already use nightly build to test this new feature:
- https://ci.apache.org/projects/jmeter/nightlies/
*** This bug has been marked as a duplicate of bug 62861 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63535] More than 50000 connects were created when I run test
with 100 threads
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63535
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FixedInTrunk
--
You are receiving this mail because:
You are the assignee for the bug.