[
https://issues.apache.org/jira/browse/BOOKKEEPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508568#comment-13508568
]
Hudson commented on BOOKKEEPER-351:
-----------------------------------
Integrated in bookkeeper-trunk #835 (See
[https://builds.apache.org/job/bookkeeper-trunk/835/])
BOOKKEEPER-351: asyncAddEntry should not throw an exception (Matteo Merli
via sijie) (Revision 1416352)
Result = UNSTABLE
sijie :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/BookKeeperTest.java
> asyncAddEntry should not throw an exception
> -------------------------------------------
>
> Key: BOOKKEEPER-351
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-351
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-351-asyncAddEntry-should-not-throw-an-exc.patch,
> 0001-BOOKKEEPER-351-asyncAddEntry-should-not-throw-an-exc.patch
>
>
> There are cases where LedgerHandle.asyncAddEntry() fails with a
> RuntimeException that is thrown by executor.submit().
> It should better invoke the callback with a failure result.
--
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
