You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2012/12/03 03:57:58 UTC
[jira] [Commented] (BOOKKEEPER-351) asyncAddEntry should not throw
an exception
[ https://issues.apache.org/jira/browse/BOOKKEEPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508441#comment-13508441 ]
Matteo Merli commented on BOOKKEEPER-351:
-----------------------------------------
[~hustlmsp] I've updated the test case with the above suggestions. Thanks for reminding this, I had it forgotten.
> 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