You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2010/02/17 12:55:27 UTC

[jira] Commented: (DOSGI-63) The discovery can be used be used before the connection to the server is completely established

    [ https://issues.apache.org/jira/browse/DOSGI-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834744#action_12834744 ] 

David Bosschaert commented on DOSGI-63:
---------------------------------------

Patch applied with many thanks.
I guess I'll leave this bug open until the proper solution is applied...

> The discovery can be used be used before the connection to the server is completely established
> -----------------------------------------------------------------------------------------------
>
>                 Key: DOSGI-63
>                 URL: https://issues.apache.org/jira/browse/DOSGI-63
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>          Components: Discovery
>    Affects Versions: 1.2
>            Reporter: Marc Schaaf
>            Assignee: David Bosschaert
>         Attachments: connection_establish_timeout.patch
>
>
> The Zookeeper Discovery is configured via the Configuration Admin and is automatically started once it receives the first configuration. At the same time as  the connection is established, the discovery registers the EndpointListener Service and the EndpointListener ServiceTracker. Under some circumstances this causes immediate calls to the discovery. However as the connection attempt is made asynchronously to the other startup, the discovery calls can occur before the connection to the Zookeeper server was established which causes them to fail. 
> An approach to solve this issue would be to wait with the registration of the EndpointListener Service and the Service Tracker until the connection could be established. Furthermore they should be unregistered once the connection to the server is lost. And registered once it is reestablished.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.