[
https://issues.apache.org/jira/browse/BOOKKEEPER-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly reopened BOOKKEEPER-5:
---------------------------------
This issue still seems to be hitting if you run for long enough. To repro,
true; while [ $? = 0 ]; do mvn test -Dtest=BookieReadWriteTest; done
Leave this running for 5-6 hours, and the bug should hit. From looking at the
code it could be that connect is unsynchronized, so resources could be
allocated and lost by concurrent executions of connect(). I'm currently testing
a patch to see if this is the case.
> 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
> Fix For: 3.4.0
>
> Attachments: BOOKKEEPER-5.diff, 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
