[
http://jira.codehaus.org/browse/WAGON-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed WAGON-220.
----------------------------
Assignee: John Casey
Resolution: Fixed
Fix Version/s: (was: 1.0)
1.0-beta-6
I've added code to ensure the current get method instance releases its
connection when an error occurs, but I'm not sure of the wisdom of releasing
the connection before reading from the method's response body...I simply don't
know the internals of httpclient that well.
I'm closing this based on the code I added...if it's still an issue, reopen it
and we should start from a failing test case.
> Wagon HTTP Deadlocks under high load
> ------------------------------------
>
> Key: WAGON-220
> URL: http://jira.codehaus.org/browse/WAGON-220
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
> Affects Versions: 1.0-beta-3
> Reporter: James William Dumay
> Assignee: John Casey
> Fix For: 1.0-beta-6
>
> Attachments: 06130051-maven.txt,
> maven.atlassian.com-log-20080612.txt,
> maven.atlassian.com-threaddump-20080612_20:17.txt, WAGON-220.patch
>
>
> It seems that the MultiThreadedHttpConnectionManager deadlocks under high
> load.
> See the attached thread dumps from Archiva for more information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
