[
https://issues.apache.org/jira/browse/BOOKKEEPER-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533035#comment-13533035
]
Ivan Kelly commented on BOOKKEEPER-516:
---------------------------------------
{quote}
Your patch is essentially executing sendNextRead in a separate thread, yes?
We've come across similar deadlock problems and if I remember correctly, we
ended up not testing it. I actually remember having a similar discussion with
Sijie. {quote}
Yes, we've come across this before, I couldn't remember if we could test it
that time or not. In reality i think this will be very hard to test, because it
relies on the netty connect happening very very quickly so the callback gets
executed in the same thread.
> TestSpeculativeRead failed in Jenkins
> -------------------------------------
>
> Key: BOOKKEEPER-516
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-516
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Flavio Junqueira
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-516-TestSpeculativeRead-failed-in-Jenkins.patch
>
>
> Here is the jenkins link:
> https://builds.apache.org/job/bookkeeper-trunk/org.apache.bookkeeper$bookkeeper-server/864/testReport/
> and concretely the relevant part of the stack traces:
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertTrue(Assert.java:27)
> at
> org.apache.bookkeeper.client.TestSpeculativeRead$LatchCallback.expectSuccess(TestSpeculativeRead.java:100)
> at
> org.apache.bookkeeper.client.TestSpeculativeRead.testSpeculativeReadFirstReadCompleteIsOk(TestSpeculativeRead.java:268)
> {noformat}
--
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
