hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-794) Callbacks are not invoked when the client is closed
Date Mon, 02 Aug 2010 20:28:19 GMT

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

Hadoop QA commented on ZOOKEEPER-794:
-------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12450827/ZOOKEEPER-794_3.patch
  against trunk revision 980576.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/103/console

This message is automatically generated.

> Callbacks are not invoked when the client is closed
> ---------------------------------------------------
>
>                 Key: ZOOKEEPER-794
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.3.1
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 3.3.2, 3.4.0
>
>         Attachments: ZOOKEEPER-794.patch.txt, ZOOKEEPER-794.txt, ZOOKEEPER-794_2.patch,
ZOOKEEPER-794_3.patch
>
>
> I noticed that ZooKeeper has different behaviors when calling synchronous or asynchronous
actions on a closed ZooKeeper client.
> Actually a synchronous call will throw a "session expired" exception while an asynchronous
call will do nothing. No exception, no callback invocation.
> Actually, even if the EventThread receives the Packet with the session expired err code,
the packet is never processed since the thread has been killed by the ventOfDeath. So the
call back is not invoked.

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


Mime
View raw message