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

Posted to dev@felix.apache.org by "metatech (JIRA)" <ji...@apache.org> on 2014/02/26 15:03:21 UTC

[jira] [Created] (FELIX-4436) DirectoryWatcher should not "refresh" Blueprint XML deployments on every start-up

metatech created FELIX-4436:
-------------------------------

             Summary: DirectoryWatcher should not "refresh" Blueprint XML deployments on every start-up
                 Key: FELIX-4436
                 URL: https://issues.apache.org/jira/browse/FELIX-4436
             Project: Felix
          Issue Type: Bug
          Components: File Install
    Affects Versions: fileinstall-3.2.4
         Environment: ServiceMix 4.5.3
            Reporter: metatech
            Priority: Minor


DirectoryWatcher can auto-deploy JAR or XML files placed in a directory.
Blueprint XML files (containing for instance ActiveMQ factories or JAAS realms) are detected as "installed" on every start-up.  Prior to FELIX-2066, this had no effect.  Since FELIX-2066, bundles detected as "installed" are now forcibly "refreshed" on every start-up.  The impact is that these bundles are stopped and restarted during the container start-up.  Because there are some race conditions (see FELIX-3067), this can prevent those XML files or other bundles depending on them from fully starting.  Here is a patch which avoids restarting those bundles when they were not modified.




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)