felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (FELIX-3891) [DS] synchronization around registerService can create deadlocks
Date Sat, 02 Mar 2013 05:33:15 GMT

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

David Jencks reopened FELIX-3891:

original solution really doesn't work for concurrent register/unregister requests.
> [DS] synchronization around registerService can create deadlocks
> ----------------------------------------------------------------
>                 Key: FELIX-3891
>                 URL: https://issues.apache.org/jira/browse/FELIX-3891
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.0
> We've found a deadlock from the synchronization around the service registration.  This
particular one comes from two threads trying to activate the service concurrently.  The losing
thread came from PackageAdmin refresh bundles thread, whereas the winning thread triggered
another component creation whose activate method calls Package admin to do some work.  (this
is eclipse package admin, not sure if felix has the same problem).
> Thinking about it some more I don't think we need to synchronize, it doesn't matter which
thread wins the service registration as long as it's registered soon.

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

View raw message