cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DOSGI-6) dOSGi startup blocks in some cases when other bundles already wait for remote services
Date Wed, 24 Oct 2012 15:06:12 GMT

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

Christian Schneider commented on DOSGI-6:
-----------------------------------------

This issue is quite old. Can you check if it still occurs with version 1.3.1?
                
> dOSGi startup blocks in some cases when other bundles already wait for remote services
> --------------------------------------------------------------------------------------
>
>                 Key: DOSGI-6
>                 URL: https://issues.apache.org/jira/browse/DOSGI-6
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>            Reporter: Marc Schaaf
>            Priority: Minor
>         Attachments: Activator_ListenerHook_Bug.patch
>
>
> When the distributed OSGi bundle is deployed in an OSGi container where already one or
more bundles are waiting for remote services, the start-up blocks until the remote calls of
the other bundles are finished if the other bundles does these calls inside the callback method
of the ServiceTracker. 
> This happens because the registration of the service hook by the distributed OSGi bundle
blocks in the mentioned case. 
> It looks like the hook is instantly informed about already existing service listeners.
The hook than registers the the proxy services which causes the execution of the service listeners
of the other bundles. The other bundles than make their remote calls from within the addingService
method of the ServiceTracker. All of this seems to happen in the start-up Thread which causes
the start-up of the distributed OSGi bundle to block until the remote calls are finished.

> Placing the registration of the hook in a different thread seems to solve the issue.


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

Mime
View raw message