[
https://issues.apache.org/jira/browse/ZOOKEEPER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065790#comment-14065790
]
Bill Havanki commented on ZOOKEEPER-776:
----------------------------------------
Anyone mind if I grab this ticket? It's been idle for over 4 years, but it's
targeted for 3.5.0. I'll assign myself soon unless I hear any objections.
Fair warning: I haven't done C++ coding since the last millennium.
> 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
> Environment: OSX 10.6.3, JVM 1.6.0-20
> Reporter: Gregory Haskins
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: zookeeper-776-fix.patch, zookeeper-776-fix.patch,
> zookeeper-776-fix.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.2#6252)
