felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4436) DirectoryWatcher should not "refresh" Blueprint XML deployments on every start-up
Date Wed, 05 Mar 2014 06:40:44 GMT

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

ASF GitHub Bot commented on FELIX-4436:
---------------------------------------

GitHub user barthel opened a pull request:

    https://github.com/apache/felix/pull/3

    [FELIX-4436] handle bundle if bundle location is a opaque uri

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/barthel/felix trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/felix/pull/3.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3
    
----
commit 008c1c43aca0b8d10f54f6eb1bf55854128e1614
Author: Uwe Barthel <barthel@x-reizend.de>
Date:   2014-03-05T06:34:52Z

    [FELIX-4436] handle bundle if bundle location is a opaque uri

----


> 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
>         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)

Mime
View raw message