[
http://jira.codehaus.org/browse/WAGON-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180965#action_180965
]
John Casey commented on WAGON-220:
----------------------------------
Is this still an issue? I've added cleanupGetTransfer to the catch blocks of
getInputStream(..) on the StreamWagon, to avoid problems there, but I'm not
sure about releasing the connection from the get method just before we actually
start reading from the InputStream resulting from that GET...not sure what the
implications are for the connection maintenance, etc.
> 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
> Fix For: 1.0
>
> 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
