[jira] Commented: (ZOOKEEPER-458) connect_index in zookeeper handle might get out of bound.

[Mahadev konar (JIRA)]

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

Mahadev konar commented on ZOOKEEPER-458:
-----------------------------------------

I tried increasing the timer on waitForConnected to 20 seconds on so and it 
seems to pass the tests 4-5 times in a row. So does look like a race condition 
somewhere. 

{code}

     bool waitForConnected(zhandle_t *zh) {
-        time_t expires = time(0) + 10;
+        time_t expires = time(0) + 20;
         while(!connected && time(0) < expires) {
             yield(zh, 1);

{code}

But all the other tests work with a timeout of 10 seconds, so I am really 
suspicious of the timer being the problem.

> connect_index in zookeeper handle might get out of bound.
> ---------------------------------------------------------
>
>                 Key: ZOOKEEPER-458
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-458
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: c client
>            Reporter: Mahadev konar
>            Assignee: Steven Cheng
>             Fix For: 3.3.0
>
>         Attachments: ZOOKEEPER-458.patch, ZOOKEEPER-458.patch, 
> ZOOKEEPER-458.patch, ZOOKEEPER-458.patch, ZOOKEEPER-458.patch, 
> ZOOKEEPER-458.patch, ZOOKEEPER-458.patch
>
>
> connect_index in zookeeper handle might get out of bound. the zokoeeper_init 
> method checks for index == count and sets it to zero. If the index becomes 
> greater than count, then it will go out of bounds.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.