Let me start a Windows VM to try to reproduce. According to the trace, it's certainly related to environment (Windows, ...).
By the way, is etc folder on CIFS or a shared volume ? Regards JB On 21/11/2018 16:17, Leschke, Scott wrote: > I’ve retested this a couple of times in the last hour. It’s reasonably > repeatable but is relatively new behavior in 4.2.1 as far as I can > tell. It looks like the following is the cause of the behavior. It > appears repeatedly in the log file. > > > > 2018-11-21T09:05:29,272 | ERROR | fileinstall-C:/BAM | > fileinstall | 10 - org.apache.felix.fileinstall - > 3.6.4 | In main loop, we have serious trouble > > java.nio.file.ClosedWatchServiceException: null > > at > sun.nio.fs.AbstractWatchService.checkOpen(AbstractWatchService.java:80) > ~[?:?] > > at > sun.nio.fs.AbstractWatchService.poll(AbstractWatchService.java:97) ~[?:?] > > at > org.apache.felix.fileinstall.internal.Watcher.processEvents(Watcher.java:163) > ~[10:org.apache.felix.fileinstall:3.6.4] > > at > org.apache.felix.fileinstall.internal.WatcherScanner.scan(WatcherScanner.java:63) > ~[10:org.apache.felix.fileinstall:3.6.4] > > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:311) > [10:org.apache.felix.fileinstall:3.6.4] > > > > Scott > > > > *From:* Leschke, Scott <[email protected]> > *Sent:* Tuesday, November 20, 2018 8:05 AM > *To:* [email protected] > *Subject:* RE: Hmm, that's new. Felix Fileinstall > > > > I’m curious if anybody else has seen the following? Is this new and > expected behavior? > > > > Scott > > > > *From:*Leschke, Scott [mailto:[email protected]] > *Sent:* Friday, November 16, 2018 3:46 PM > *To:* [email protected] <mailto:[email protected]> > *Subject:* Hmm, that's new. Felix Fileinstall > > > > Question. I’ve been running v 4.2.1 under Java 10.0.2 for a while in my > test environment and everything has been working as expected. Recently > though, it appeared that fileinstall wasn’t picking up that .jar and > .cfg files we being changed via hot deploy. > > > > I tried various things to get it to work but finally thought I’d do a > fresh install of 4.2.1 to see if that might clear things up. To install, > I run a PowerShell script that unzips the apache-karaf-4.2.1.zip file, > installs the features I need and then I change where Karaf’s hot deploy > folder is by replacing etc/org.apache.felix.fileinstall-deploy.cfg with > my own file, org.apache.felix.fileinstall-bam.cfg. > > > > My application deploy folder is a hierarchy rooted at the folder “BAM” > (Business Activity Monitoring) that has 3 subfolders in it, > > */runtime/* (for bundles (jars) the app is dependent on), > */datasources/* (where I keep the .cfgs that contain the > org.ops4j.datasource-*.cfg files the app needs), and */systems/* which > is another folder hierarchy containing .cfg files and subfolders > containing files associated with a system. > > > > After the install, I’m seeing some “pseudo” bundles with the names and > versions shown below. > > > > C__BAM_runtime 0.0.0 > > C__BAM_datasources 0.0.0 > > Wrap_jardir_C__BAM_systems 0 > > > > I’ve rerun the install a few times with some varying results. In one > case, the last name was in line with the others and was shown as > C__BAM_systems. In another case, none of those bundles existed at all? > Thoughts? > > > > Windows Server 2016 BTW. Sorry for the copius detail but I’m trying to > be clear as to what I’m seeing. > > > > Scott > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
