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

Uwe Barthel edited comment on FELIX-4436 at 3/19/14 8:51 PM:
-------------------------------------------------------------

[~metatech] Oh, that isn't cool.
Please provide information about your framework and setup.
Debug log information are helpful too.
Is it possible that you provide the bundle cache content for that file ?
It sounds like a failure in scanner on calculate the checksum or something else 
in this context.

Under Linux with a minimal Felix setup I have not noticed this behavior.

Please retry with a clear bundle cache.



was (Author: barthel):
[~metatech] Oh, that isn't cool.
Please provide information about your framework and setup.
Debug log information are helpful too.

It sounds like a failure in scanner on calculate the checksum.

Under Linux with a minimal Felix setup I have not noticed this behavior.

Please retry with a clear bundle cache.



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

Reply via email to