[jira] [Commented] (FELIX-3746) Deadlock around SCR AbstractComponentManager and DelayedComponentManager

["David Jencks (JIRA)" <ji...@apache.org>]

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

David Jencks commented on FELIX-3746:
-------------------------------------

I think this is a duplicate of https://issues.apache.org/jira/browse/FELIX-3687.  see the bu thread.  In any case you are running against very old DS code and most of the problematic locking has been removed.  We stopped seeing this deadlock in the stress tests for FELIX-3680.  Please try again with trunk.
                
> Deadlock around SCR AbstractComponentManager and DelayedComponentManager
> ------------------------------------------------------------------------
>
>                 Key: FELIX-3746
>                 URL: https://issues.apache.org/jira/browse/FELIX-3746
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.6.0
>            Reporter: Bertrand Delacretaz
>         Attachments: stack-trace.txt
>
>
> The exact affected version is org.apache.felix.scr trunk revision 1236132
> I'm running my stress tests from https://github.com/bdelacretaz/osgi-stresser which repeatedly and concurrently change the start level, update a bundle and stop/start bundles, and sometimes seeing a deadlock between threads that use the AbstractComponentManager and DelayedComponentManager.
> I'll attach a stack trace that's slightly incomplete, where I removed product-specific threads. I can provide the full stack trace privately if needed.
> I'll try running the latest trunk of that module to see if that makes a difference.

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