[
https://issues.apache.org/jira/browse/ZOOKEEPER-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921939#action_12921939
]
Michi Mutsuzaki commented on ZOOKEEPER-794:
-------------------------------------------
ZOOKEEPER-794_5.patch.txt doesn't compile. I'm getting these errors:
[javac]
branch-3.3/src/java/test/org/apache/zookeeper/test/SessionTest.java:201: cannot
find symbol
[javac] symbol : variable Assert
[javac] location: class org.apache.zookeeper.test.SessionTest
[javac] Assert.fail("Should have received a SessionExpiredException");
[javac] ^
[javac]
branch-3.3/src/java/test/org/apache/zookeeper/test/SessionTest.java:217: cannot
find symbol
[javac] symbol : variable Assert
[javac] location: class org.apache.zookeeper.test.SessionTest
[javac] Assert.assertEquals(KeeperException.Code.SESSIONEXPIRED.toString(),
cb.toString());
[javac] ^
We need to either:
a. import org.junit.Assert, or
b. Use fail/assertEquals instead of Assert.fail/Assert.assertEquals.
--Michi
> 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
> Priority: Blocker
> Fix For: 3.3.2, 3.4.0
>
> Attachments: ZOOKEEPER-794.patch.txt, ZOOKEEPER-794.txt,
> ZOOKEEPER-794_2.patch, ZOOKEEPER-794_3.patch, ZOOKEEPER-794_4.patch.txt,
> ZOOKEEPER-794_5.patch.txt
>
>
> 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.
