[
https://issues.apache.org/jira/browse/ZOOKEEPER-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148731#comment-13148731
]
Thomas Koch commented on ZOOKEEPER-1251:
----------------------------------------
Only for correctness: The bug has probably already been there before in the
case of read requests. I could provide a patch on top of ZOOKEEPER-1284 if you
like. But since the issue you describe has not been introduced by
ZOOKEEPER-1251, I propose that we handle this in a new issue?
> call checkSession at begin of PrepRequestProcessor.pRequest
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-1251
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1251
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Thomas Koch
> Assignee: Thomas Koch
> Attachments: ZOOKEEPER-1251.patch
>
>
> There are 6 locations that call checkSession. This can be reduced to one
> location and makes it also much clearer in which cases checkSession is called
> or not called.
> Note that in case that now the SessionMoved|Expired error is checked first
> before the check for a Marshalling error. However it shouldn't matter which
> error gets reported.
--
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
