[
https://issues.apache.org/jira/browse/HTTPASYNC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated HTTPASYNC-59:
----------------------------------
Attachment: 2-2.png
2-1.png
1-2.png
1-1.png
In 1-1 thread "A" tries to synchronize on the object already locked by 2-2
In 2-1 thread "B" tries to synchronize on the object already locked by 1-2
--> deadlock
> Deadlock when creating new connections
> --------------------------------------
>
> Key: HTTPASYNC-59
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-59
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta4
> Reporter: Robert Stupp
> Attachments: 1-1.png, 1-2.png, 2-1.png, 2-2.png
>
>
> Two threads can produce a deadlock with the following stack traces (see
> attached images).
> I have no JUnit for it - it is a test that performs a huge number of HTTP
> requests (without proxies) in a few concurrent threads.
> Configuration is basically the same as in HTTPASYNC-57
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
