You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Shevek (JIRA)" <ji...@apache.org> on 2013/04/02 23:53:15 UTC
[jira] [Updated] (CURATOR-13) KillSession does not work if
ZooKeeper does not allow sessionId in constructor
[ https://issues.apache.org/jira/browse/CURATOR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shevek updated CURATOR-13:
--------------------------
Description:
https://issues.apache.org/jira/browse/ZOOKEEPER-1680
The ticket linked above suggests that KillSession is broken, as it's impossible to construct a duplicate session.
Background: KillSession works by creating a duplicate session and closing it. If a duplicate session cannot be created, it won't work.
was:
https://issues.apache.org/jira/browse/ZOOKEEPER-1680
The ticket linked above suggests that KillSession is broken, as it's impossible to construct a duplicate session.
> KillSession does not work if ZooKeeper does not allow sessionId in constructor
> ------------------------------------------------------------------------------
>
> Key: CURATOR-13
> URL: https://issues.apache.org/jira/browse/CURATOR-13
> Project: Apache Curator
> Issue Type: Bug
> Reporter: Shevek
> Assignee: Jordan Zimmerman
>
> https://issues.apache.org/jira/browse/ZOOKEEPER-1680
> The ticket linked above suggests that KillSession is broken, as it's impossible to construct a duplicate session.
> Background: KillSession works by creating a duplicate session and closing it. If a duplicate session cannot be created, it won't work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira