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

Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2013/01/31 19:11:12 UTC

[jira] [Commented] (FELIX-3807) Refreshing bundles should first grab all the bundle locks to avoid concurrent modifications of those bundles

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

Richard S. Hall commented on FELIX-3807:
----------------------------------------

I needed to commit one additional patch to not call stop() on an uninstalled bundle, since this throws an exception which causes us to fire a framework event, which ultimately caused us to fail a CT test that was only expecting one framework event. Nothing major.
                
> Refreshing bundles should first grab all the bundle locks to avoid concurrent modifications of those bundles
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-3807
>                 URL: https://issues.apache.org/jira/browse/FELIX-3807
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: framework-4.2.0
>
>
> This will avoid possible problems where bundles states can change between stopping the bundle and actually refreshing them.

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