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:57 UTC

[jira] [Updated] (ZOOKEEPER-776) API should sanity check sessionTimeout argument

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

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

> API should sanity check sessionTimeout argument
> -----------------------------------------------
>
>                 Key: ZOOKEEPER-776
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-776
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: c client, java client
>    Affects Versions: 3.2.2, 3.3.0, 3.3.1, 3.4.6, 3.5.0
>         Environment: OSX 10.6.3, JVM 1.6.0-20
>            Reporter: Gregory Haskins
>            Assignee: Raul Gutierrez Segales
>            Priority: Minor
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: zookeeper-776-fix.patch, zookeeper-776-fix.patch, zookeeper-776-fix.patch, ZOOKEEPER-776.patch
>
>
> passing in a "0" sessionTimeout to ZooKeeper() constructor leads to errors in subsequent operations.  It would be ideal to capture this configuration error at the source by throwing something like an IllegalArgument exception when the bogus sessionTimeout is specified, instead of later when it is utilized.



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