[
https://issues.apache.org/jira/browse/BOOKKEEPER-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051506#comment-13051506
]
Flavio Junqueira commented on BOOKKEEPER-5:
-------------------------------------------
Good catch, Ivan. It is actually not even necessary to connect before invoking
an operation, since we call connectIfNeededAndDoOp() upon every addEntry and
readEntry. It works even without the else block in your version of the patch.
There are also a few other changes unrelated to this issue, like a change to
pom.xml and fixed typos. Do you want those to get in or they ended up there by
accident?
> 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.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
