[
https://issues.apache.org/jira/browse/HTTPCLIENT-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579611#action_12579611
]
Oleg Kalnichevski commented on HTTPCLIENT-759:
----------------------------------------------
Good catch, Sam
Unfortunately one of the new test cases fails for me. (Ubuntu Linux 7.10; Java
1.5.0.11; single-core Intel Centrino)
Tests run: 323, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.899 sec <<<
FAILURE!
testAbortInAllocate(org.apache.http.impl.client.TestDefaultClientRequestDirector)
Time elapsed: 1.019 sec <<< FAILURE!
junit.framework.AssertionFailedError: should have finished get request
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.apache.http.impl.client.TestDefaultClientRequestDirector.testAbortInAllocate(TestDefaultClientRequestDirector.java:110)
Oleg
> DefaultClientRequestDirector doesn't release connections back to
> ClientConnectionManager on exceptions
> ------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-759
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-759
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.0 Alpha 3
> Reporter: Sam Berlin
> Attachments: changes.txt
>
>
> See HTTPCLIENT-747 for more info. Basically the deal is that an entry is
> always allocated, but currently it's only released if execute(..) completes
> normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
