[
https://issues.apache.org/jira/browse/FELIX-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231292#comment-13231292
]
Richard S. Hall commented on FELIX-2787:
----------------------------------------
Depends on how it is implemented, but I'm not certain. For example, if the
framework is shutting down and it's start level is at 1 when the shutdown
begins. I believe it will stay at 1 until it has shutdown all active bundles
with start level 1. Assume the "active level" of File Install is set to 1 and
that we have 1000 active bundles and File Install will be the last bundle
stopped.
The situation we saw was the File Install was restarting bundles that the
framework was stopping, e.g., framework stops bundle 999, then File Install
restarts bundle 999, etc. The key here is not the start level, but that the
framework state is "STOPPING" and therefore File Install should do no
management at all at that time. Likewise when the framework is "STARTING".
> [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
