[
https://issues.apache.org/jira/browse/ZOOKEEPER-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148750#comment-13148750
]
Patrick Hunt commented on ZOOKEEPER-1251:
-----------------------------------------
@thomas I checked your assertion about "probably already been there before in
the case of read requests" by updating my test in ZOOKEEPER-1208 to do a read -
doesn't seem to be the case. Reads and writes are handled gracefully when
operations come in after session expiration.
> 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
