Bug 41457 - TCPSampler re-uses socket connection. This is not always desirable.
Summary: TCPSampler re-uses socket connection. This is not always desirable.
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.2
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-24 17:04 UTC by john.neale
Modified: 2007-01-31 12:47 UTC (History)
0 users


Attachments
Patch to implement this enhancement (10.12 KB, patch)
2007-01-24 20:32 UTC, john.neale 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description john.neale 2007-01-24 17:04:01 UTC 
I have an application to test that requires only one conversation per socket
connection. Currently, TCPSampler re-uses sockets for multiple conversations.
I've added an enhancement to select whether to re-use the socket or create a new
socket for each conversation.

Patch is attached.
Comment 1 john.neale 2007-01-24 20:32:08 UTC 
Created attachment 19452 [details]
Patch to implement this enhancement

Adds a Re-Use Connection checkbox to the TCLSampler. If checked (the default)
then the TCPSampler will re-use the same connection in each loop for each
thread. If not checked TCPSampler will open a new connection with each loop.
Comment 2 Sebb 2007-01-31 12:47:34 UTC 
Thanks for the patches.

I had to change the TCPConfig patch slightly to ensure that existing test 
plans (without the new variable) retained the original behaviour.

The next nightly build dated after this update will contain the fix:

http://people.apache.org/builds/jakarta-jmeter/nightly/
Comment 3 The ASF infrastructure team 2022-09-24 20:37:38 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1853