[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872400#action_12872400
 ] 

Benjamin Reed commented on ZOOKEEPER-776:
-----------------------------------------

you were a little over ambitious gregory :) you don't need to load from a 
properties file. just check the system property and if it isn't sent (or not a 
number) use 100.

are you going to be able to patch the C client too?

> 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.4.0
>
>         Attachments: 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to