[
https://issues.apache.org/jira/browse/ZOOKEEPER-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139357#comment-13139357
]
Marshall McMullen commented on ZOOKEEPER-1248:
----------------------------------------------
I think this was an artifact of one of my original implementations for multi to
try to propagate failures out properly. Nice catch on cleaning this up.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
