[
https://issues.apache.org/jira/browse/HTTPCORE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-331.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.3-alpha2
4.2.4
I think this change alone should have fixed the problem [1]. But fundamentally
there is no reason why future notifications should be executed within a
synchronized block (those callbacks can be massively complex and should not
lock other threads from accessing future's internal state). Fixed by [2].
Could you please re-test your application with the latest 4.2.x snapshot and
confirm whether or not the problem has been fixed?
Oleg
[1] http://svn.apache.org/viewvc?rev=1435160&view=rev
[2] http://svn.apache.org/viewvc?rev=1435144&view=rev
http://svn.apache.org/viewvc?rev=1435147&view=rev
> deadlock in AbstractNIOConnPool
> -------------------------------
>
> Key: HTTPCORE-331
> URL: https://issues.apache.org/jira/browse/HTTPCORE-331
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.2.3
> Environment: jjdk 1.7.0_u10
> Reporter: Scott Stanton
> Priority: Critical
> Fix For: 4.2.4, 4.3-alpha2
>
> Attachments: stacks
>
>
> I have run into a deadlock in the AbstractNIOConnPool. I have attached the
> deadlock stacks. I'm not entirely sure what's going on yet, but it appears
> that nested futures are causing lock ordering problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
