Bug 55865 - Performance :Disable stale check by default in HttpClient 4 and 3.1
Summary: Performance :Disable stale check by default in HttpClient 4 and 3.1
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 2.9
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-09 22:53 UTC by Philippe Mouawad
Modified: 2013-12-09 22:56 UTC (History)
1 user (show)


Attachments
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 Philippe Mouawad 2013-12-09 22:53:06 UTC 
Profiling JMeter, I noticed an important number of SocketTimeoutException being triggered without any impact on response status.

I investigated it a bit deeper and find out it affected only HttpClient implementations.
Looking a bit deeper, it is due to connection stale check which is enabled by default.
This check sets a timeout to 1ms , see :
- org.apache.http.impl.io.SocketInputBuffer#isDataAvailable
- org.apache.http.impl.AbstractHttpClientConnection#isStale


I wonder if it's a good idea to keep it enabled by default as with high number of Threads and throughput it means a huge number of Exception.
Comment 1 Philippe Mouawad 2013-12-09 22:56:56 UTC 
Date: Mon Dec  9 22:56:12 2013
New Revision: 1549702

URL: http://svn.apache.org/r1549702
Log:
Bug 55865 - Performance :Disable stale check by default in HttpClient 4 and 3.1
Bugzilla Id: 55865

Modified:
    jmeter/trunk/bin/hc.parameters
    jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java
    jmeter/trunk/xdocs/changes.xml
Comment 2 The ASF infrastructure team 2022-09-24 20:37:56 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3286