[
https://issues.apache.org/jira/browse/FELIX-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339199#comment-16339199
]
Darko Tominac edited comment on FELIX-4906 at 1/25/18 1:17 PM:
---------------------------------------------------------------
Additional info: hot deployment works fine for a few hours after
ServiceMix/Karaf restart. But than it just "stops monitoring" deployment
directory. It does not detect bundle update or removal.
Restarting ServiceMix helps but only for short time.
*felix.fileinstall.disableNio2 = true* is still a valid workaround.
was (Author: dtominac):
Additional info: hot deployment works for a few hours after ServiceMix/Karaf
restart.
But than it just "stops monitoring" deployment directory. It does not detect
bundle update or removal.
Restarting ServiceMix helps but only for short time.
*felix.fileinstall.disableNio2 = true* is still a valid workaround.
> 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)
