Mailing-List: contact zookeeper-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-dev@hadoop.apache.org
Message-ID: <234002551.1214578726663.JavaMail.jira@brutus>
Date: Fri, 27 Jun 2008 07:58:46 -0700 (PDT)
From: "Benjamin Reed (JIRA)" <jira@apache.org>
To: zookeeper-dev@hadoop.apache.org
Subject: [jira] Commented: (ZOOKEEPER-47) io thread still around after a
 EXPIRED_SESSION or AUTH_FAILED event is received
In-Reply-To: <298258147.1213825545328.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Reed commented on ZOOKEEPER-47:
----------------------------------------

You're right. I was reading the code wrong.

> io thread still around after a EXPIRED_SESSION or AUTH_FAILED event is received
> -------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-47
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-47
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: c client
>            Reporter: Benjamin Reed
>
> If a session expires, the zhandle_t becomes invalid and useless; however, the io thread keeps going.
> do_io in mt_adaptor.c needs to check the return code of zookeeper_interest and zookeeper_process and get out of the loop if the handle is invalid.

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