tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-279) If getTransactionAwareName() throws an exception, abort() does not happen
Date Fri, 23 Mar 2018 19:49:00 GMT

    [ https://issues.apache.org/jira/browse/TEPHRA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411951#comment-16411951
] 

ASF GitHub Bot commented on TEPHRA-279:
---------------------------------------

Github user anew commented on the issue:

    https://github.com/apache/incubator-tephra/pull/69
  
    rebased on current master - waiting for one more build before committing this. 


> If getTransactionAwareName() throws an exception, abort() does not happen
> -------------------------------------------------------------------------
>
>                 Key: TEPHRA-279
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-279
>             Project: Tephra
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.13.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Andreas Neumann
>            Priority: Major
>
> The problem is here in TransactionContext:
> {code}
>   private void checkForConflicts() throws TransactionFailureException {
>     Collection<byte[]> changes = Lists.newArrayList();
>     for (TransactionAware txAware : txAwares) {
>       try {
>         changes.addAll(txAware.getTxChanges());
>       } catch (Throwable e) {
>         // ---- PROBLEM: if getTransactionAwareName() throws, abprt() is not called!
>         String message = String.format("Unable to retrieve changes from transaction-aware
'%s' for transaction %d. ",
>                                        txAware.getTransactionAwareName(), currentTx.getTransactionId());
>         LOG.warn(message, e);
>         abort(new TransactionFailureException(message, e));
>         // abort will throw that exception
>       }
>     }
> {code}
> We could consider such a transaction-aware ill-behaved, but we should still make sure
the transaction semantics remain correct. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message