You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Amichai Rothman (JIRA)" <ji...@apache.org> on 2013/06/13 20:29:20 UTC

[jira] [Resolved] (DOSGI-191) ZooKeeperDiscovery instance reconnects to ZooKeeper after bundle is stopped

     [ https://issues.apache.org/jira/browse/DOSGI-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amichai Rothman resolved DOSGI-191.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0

Fixed, although the ZK event thread is still not being shut down - that is the ZOOKEEPER-795 bug. I'm closing this issue anyway under the assumption that we'll be upgrading the ZK dependency library to a newer version in any case when the new release comes out.
                
> ZooKeeperDiscovery instance reconnects to ZooKeeper after bundle is stopped
> ---------------------------------------------------------------------------
>
>                 Key: DOSGI-191
>                 URL: https://issues.apache.org/jira/browse/DOSGI-191
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>          Components: Discovery
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Amichai Rothman
>            Assignee: Amichai Rothman
>             Fix For: 1.5.0
>
>
> After the ZooKeeper discovery bundle is stopped, which also closes the ZooKeeper instance, ZooKeeperDiscovery still gets the Expired notification from ZK, but then goes on to create a new ZooKeeper instace and start it.
> This also relates to ZOOKEEPER-795, which was fixed on a later version than the one we use.

--
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