Gregory Haskins commented on ZOOKEEPER-776:

Ah, sorry, I had already deleted it before I saw your latest comment.  I seem 
to be making a general mess of this JIRA entry.  Bear with me while I learn :)

In any case, I have submitted a fix that has a JUnit and a --no-prefix export, 
so hopefully Hudson is happier this time.  I confirmed that the test fails 
without the fix, and passes with the fix.  Let me know if there is anything 
else I should be doing.

Thanks for all the help,

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