You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:21:56 UTC

[jira] [Updated] (ZOOKEEPER-1248) multi transaction sets request.exception without reason

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han updated ZOOKEEPER-1248:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> multi transaction sets request.exception without reason
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-1248
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1248
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Thomas Koch
>            Assignee: Thomas Koch
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-1248.patch, ZOOKEEPER-1248.patch, ZOOKEEPER-1248.patch
>
>
> I'm trying to understand the purpose of the exception field in request. This isn't made easier by the fact that the multi case in PrepRequestProcessor sets the exception without reason.
> The only code that calls request.getException() is in FinalRequestProcessor and this code only acts when the operation _is not_ a multi operation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)