Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
4.2.3
-
None
-
jjdk 1.7.0_u10
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
HTTPCLIENT-1314 Deadlock in http.client.fluent.Async.ExecRunnable.run() if there is an exception in FutureCallback
- Closed