felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3807) Refreshing bundles should first grab all the bundle locks to avoid concurrent modifications of those bundles
Date Thu, 13 Dec 2012 16:46:12 GMT

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

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

Ok, I think I understand. The refresh thread only calls stop if it needs to and thus only
acquires the bundle lock if it needs to, which allows the other thread to start it after the
refresh thread has checked to see if it is stopped. I think the simple solution here is to
always call stop regardless, which would give the bundle lock holder time to finish.
                
> 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
>
> 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

Mime
View raw message