Bug 47817 - Use multiple connections per thread
Summary: Use multiple connections per thread
Status: RESOLVED DUPLICATE of bug 50943
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement with 1 vote (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 08:30 UTC by jvangaalen
Modified: 2012-04-28 14:48 UTC (History)
2 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jvangaalen 2009-09-10 08:30:17 UTC
As a standard for HTTP/1.1 the browser can use 2 simultaneous connections to the server to do its requests. Currently a single threads seems to use just only one connections to the server. To make testing more realistic a thread / user should be able to use 2 simultaneous connections to retrieve objects.

For the latest versions of Firefox it is even using up to 6 connections simultaneously. To make tests realistic, this woould definitly be a must. Especially for HTTPS it is more realistic because it involves SSL handshakes. Also many webservers are configured to hold a maximum of X connections, and when simultaneous connetions are used you would hit this twice as fast as when testing with only 1 connection (as JMeter does now).
Comment 1 Peter Martinovic 2010-11-08 05:52:05 UTC
We consider this feature very important, e.g. AJAX/GWT pages that execute commands in parralel cannot be now precisely simulated with JMeter. Commands that usually occur in conflicting times, JMeter executes sequentially.
Comment 2 Philippe Mouawad 2012-04-28 14:48:53 UTC
First Requirement has been implemented as Concurrent Download.
I will open a new Bug for second issue

*** This bug has been marked as a duplicate of bug 50943 ***
Comment 3 The ASF infrastructure team 2022-09-24 20:37:43 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2275