[
https://issues.apache.org/jira/browse/HTTPASYNC-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086592#comment-17086592
]
Oleg Kalnichevski commented on HTTPASYNC-160:
---------------------------------------------
> Just one thing, that since now it will go in the failed section of the code.
> If we had already closed the connection manager etc. by then it should not
> get affected
I do not think this matters. The exchange will fail immediately without any
making any attempts to lease a connection or allocate any other resources.
Oleg
> InternalHttpAsyncClient doesn't close gracefully
> ------------------------------------------------
>
> Key: HTTPASYNC-160
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-160
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1.4
> Reporter: Anurag Agarwal
> Priority: Minor
> Fix For: 4.1.5, HttpClient 5.0
>
>
> InternalHttpAsyncClient:123 -> uses ensureRunning()
> This checks if the status of the client is active / stopped.
> Let us say a thread initiated a quested and before reaching this line, close
> is called as well on the client.
> Now ensureRunning call will fail but with a RuntimeException, leading to I/O
> Reactor failure and it won't be a graceful shutdown of the client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
