[ https://issues.apache.org/jira/browse/ZOOKEEPER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593423#comment-14593423 ]
Bill Havanki commented on ZOOKEEPER-776: ---------------------------------------- No worries! I've been working on other things, so I haven't been blocked at all. Thanks for taking this issue back up! > 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.2, 3.6.0 > > Attachments: ZOOKEEPER-776.patch, 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.3.4#6332)