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 (Reopened) (JIRA)" <ji...@apache.org> on 2012/03/16 22:01:40 UTC

[jira] [Reopened] (FELIX-2787) [File Install] Do not perform management activities while framework is starting/stopping

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

Richard S. Hall reopened FELIX-2787:
------------------------------------


Re-open for now to verify whether it is still an issue or not.
                
> [File Install] Do not perform management activities while framework is starting/stopping
> ----------------------------------------------------------------------------------------
>
>                 Key: FELIX-2787
>                 URL: https://issues.apache.org/jira/browse/FELIX-2787
>             Project: Felix
>          Issue Type: Improvement
>          Components: File Install
>    Affects Versions: fileinstall-3.1.4
>            Reporter: Richard S. Hall
>            Assignee: Guillaume Nodet
>
> File Install has been known to cause deadlocks, race conditions, and other sorts of spurious issues. One of the main reasons for this is that File Install is pretty aggressive in its management of bundles. This has caused us to improve the framework to deal with its aggressiveness, but still it is not perfect. We have seen people wanting to introduce a delay value for management, etc. We also see issues where the framework is trying to shut down and File Install is going right behind the framework restarting bundles as the framework stops them. It would be better if File Install monitored the starting/stopping status for the framework and only performed its management activities while the framework were active. This means File Install's management threads should not do their processing when the framework is not in the ACTIVE state. This will be a good improvement, although it won't completely eliminate the window, since this is a check-then-act situation. However, as long as the threads check the status on each process loop, the window will be significantly reduced.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira