[
https://issues.apache.org/jira/browse/BOOKKEEPER-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506404#comment-13506404
]
Ivan Kelly commented on BOOKKEEPER-485:
---------------------------------------
Ok, so it's similar to BOOKKEEPER-5, but not the same. Basically, there's a
race between closing the PerChannelBookieClient and the connection completing.
If the PerChannelBookieClient requests to connect, and then is closed before
the request completes, then the channel object returned on successful
connection is orphaned. The fix is simple, im running in loop now. A succinct
repo should be easy enough to implement as well.
> TestFencing hung
> ----------------
>
> Key: BOOKKEEPER-485
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-485
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Flavio Junqueira
> Priority: Critical
> Attachments: stack-trace-hung.txt
>
>
> ... while testing BOOKKEEPER-477, but I think they are unrelated.
--
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
