[
https://issues.apache.org/jira/browse/DOSGI-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861526#action_12861526
]
Marc Schaaf commented on DOSGI-70:
----------------------------------
With regard to the discussion on the mailing list:
As far as I see it, it is not possible to "simply" reconnect once the session
with the Zookeeper server has expired as all the registered watches probably
need to be reregistered. However based on the response from the Zookeeper guys,
the session timeout could be increased to at least avoid this issue for the
moment. Unfortunately the discovery currently doesn't provide any configuration
option for it, so you would have to change this in the source code. However it
shouldn't be too hard to add this configuration option to the Zookeeper
discovery.
In general I agree that the connection management of the discovery
implementation needs to be enhanced!
Cheers,
Marc
> Reconnect automatically to Zookeeper after a connection loss / timeout
> ----------------------------------------------------------------------
>
> Key: DOSGI-70
> URL: https://issues.apache.org/jira/browse/DOSGI-70
> Project: CXF Distributed OSGi
> Issue Type: Improvement
> Components: Discovery
> Affects Versions: 1.0, 1.1, 1.2
> Reporter: Julien Vey
>
> When a remote service is disconnected from the ZooKeeper Server and when the
> session is expired, it should be able to try to reconnect automatically.
> Here the discussion on the mailing list :
> http://old.nabble.com/DOSGI-Discovery-with-Zookeeper%2C-re-establish-session-after-a-timeout-tt28305408.html
>
> Some links to zookeeper about this matter
> http://wiki.apache.org/hadoop/ZooKeeper/FAQ#A3
> http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
