You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Darko Tominac (JIRA)" <ji...@apache.org> on 2018/01/25 11:53:00 UTC
[jira] [Commented] (FELIX-4906) Changes in symlinked bundles not
detected with NIO2 WatcherScanner
[ https://issues.apache.org/jira/browse/FELIX-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339118#comment-16339118 ]
Darko Tominac commented on FELIX-4906:
--------------------------------------
This bug is still present in fileinstall 3.6.4.
OS: SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 0
Java: java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
Product: ServiceMix 6.3.1 with fileinstall updated to 3.6.4
ServiceMix is installed on *remote file system, mounted locally* on /aplik directory.
Workaround:
in file org.apache.felix.fileinstall-deploy.cfg set
*felix.fileinstall.disableNio2 = true*
> Changes in symlinked bundles not detected with NIO2 WatcherScanner
> ------------------------------------------------------------------
>
> Key: FELIX-4906
> URL: https://issues.apache.org/jira/browse/FELIX-4906
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Affects Versions: fileinstall-3.4.0, fileinstall-3.4.2, fileinstall-3.5.0
> Reporter: Tim Hull
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: fileinstall-3.6.4
>
>
> Since the new NIO2 WatcherScanner was introduced as part of FileInstall 3.4.0, I've noticed that FileInstall no longer detects changes to files symbolically linked to from the deploy directory. Also, there may be additional issues with network-mounted directories as well. These can be worked around by setting the felix.fileinstall.disableNio2 option to true, though this isn't ideal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)