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

Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2012/06/12 20:32:43 UTC

[jira] [Created] (ZOOKEEPER-1485) client xid overflow is not handled

Michi Mutsuzaki created ZOOKEEPER-1485:
------------------------------------------

             Summary: client xid overflow is not handled
                 Key: ZOOKEEPER-1485
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1485
             Project: ZooKeeper
          Issue Type: Bug
          Components: c client, java client
    Affects Versions: 3.3.5, 3.4.3
            Reporter: Michi Mutsuzaki


Both Java and C clients use signed 32-bit int as XIDs. XIDs are assumed to be non-negative, and zookeeper uses some negative values as special XIDs (e.g. -2 for ping, -4 for auth). However, neither Java nor C client ensures the XIDs it generates are non-negative, and the server doesn't reject negative XIDs.

Pat had some suggestions on how to fix this:

- (bin-compat) Expire the session when the client sends a negative XID.
- (bin-incompat) In addition to expiring the session, use 64-bit int for XID so that overflow will practically never happen.

--Michi

--
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