[
https://issues.apache.org/jira/browse/BOOKKEEPER-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056300#comment-13056300
]
Benjamin Reed commented on BOOKKEEPER-5:
----------------------------------------
if i understand this patch correctly, there are two big fixes:
1) we wait for close to complete
2) we proactively initiate a connection on lookup
was 1) really causing a problem?
the rest is really just cleanup right?
it looks like all of the additions to BookKeeper.java are just debug messages
that should be removed.
other than these small items the patch looks good.
> Issue with Netty in BookKeeper
> ------------------------------
>
> Key: BOOKKEEPER-5
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-5
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Attachments: BOOKKEEPER-5.diff, BOOKKEEPER-5.diff,
> BOOKKEEPER-5.patch, BOOKKEEPER-5.patch, ZOOKEEPER-998.patch
>
>
> In one my experiments, I found that a BookKeeper object was locked after I
> tried to halt it. By searching the Web, I found that the issue is described
> here:
> http://www.jboss.org/netty/community.html#nabble-td5492010
> I'll upload a patch to fix it. For now, I'm marking it for 3.4.0, but if
> there is any chance we can get it in 3.3.3, it would be nice.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
