Bug 58947 - Connect metric is wrong when ConnectException occurs

Bugzilla Id: 58947

git-svn-id: https://svn.apache.org/repos/asf/jmeter/trunk@1727742 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Philippe Mouawad 2016-01-30 18:21:18 +00:00
parent 302012293e
commit 53e2acd214
2 changed files with 7 additions and 3 deletions

View File

@ -106,9 +106,12 @@ public class MeasuringConnectionManager extends PoolingClientConnectionManager {
@Override
public void open(HttpRoute route, HttpContext context, HttpParams params) throws IOException {
handler.open(route, context, params);
if (sample != null) {
sample.connectEnd();
try {
handler.open(route, context, params);
} finally {
if (sample != null) {
sample.connectEnd();
}
}
}

View File

@ -240,6 +240,7 @@ Summary
<li><bug>58209</bug>JMeter hang when testing javasampler because HashMap.put() is called from multiple threads without sync.</li>
<li><bug>58301</bug>Use typed methods such as setInt, setDouble, setDate ... for prepared statement #27</li>
<li><bug>58851</bug>Add a dependency to hamcrest-core to allow JUnit tests with annotations to work</li>
<li><bug>58947</bug>Connect metric is wrong when ConnectException occurs</li>
</ul>
<h3>Controllers</h3>