[
https://issues.apache.org/jira/browse/ZOOKEEPER-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819725#comment-13819725
]
Benjamin Jaton commented on ZOOKEEPER-1812:
-------------------------------------------
The way it's handled right now in ZooInspectorManagerImpl just cannot work :
the connection is attempted only if this.zooKeeper is null.
The first time around, this.zooKeeper is null, so it creates a new ZooKeeper
client and tries to connect, which is good.
The problem is that it never resets this.zooKeeper to null so we never enter
the <if> again.
> ZooInspector reconnection always fails if first connection fails
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-1812
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1812
> Project: ZooKeeper
> Issue Type: Bug
> Components: contrib
> Affects Versions: 3.4.5, 3.5.0
> Reporter: Benjamin Jaton
> Assignee: Benjamin Jaton
> Priority: Minor
> Labels: zooinspector
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1812-3.4.patch, ZOOKEEPER-1812.patch
>
>
> Steps to reproduce:
> - Connect to localhost:2181 when ZooKeeper server is down. After a few
> seconds, ZooInspector warns that the connection has failed
> - start the ZooKeeper server
> - Reconnect to localhost:2181, ZooInspector will still not be able to connect
> to the server.
> The workaround is to relaunch ZooInspector.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
