You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2014/04/08 16:02:14 UTC
[jira] [Resolved] (FELIX-4436) DirectoryWatcher should not refresh
transformed bundles on every start-up
[ https://issues.apache.org/jira/browse/FELIX-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved FELIX-4436.
------------------------------------
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M fileinstall/src/main/java/org/apache/felix/fileinstall/internal/DirectoryWatcher.java
Committed r1585732
> DirectoryWatcher should not refresh transformed bundles 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
> Assignee: Guillaume Nodet
> Priority: Minor
> Fix For: fileinstall-3.4.0
>
> Attachments: felix_no_refresh_installed.patch
>
>
> 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.2#6252)