Hello All,
We are observing Deployment Scanner threads keep on running so disabled it in configuration by setting value to -1 so that it will scan only during server startup.
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="-1"/>
After this change, we are still observing following threads in thread dumps.
Are these threads utilizing more CPU time (or) just I/O Wait?
xnio-file-watcher[Watcher for /data/apps/wildfly-8.2.0.Final/standalone/tmp/vfs/temp/tempe322009ef7f2906b/web.war-a2031c03cba8deaf/]-0" #134 daemon prio=5 os_prio=0 tid=0x00007f5d8c075000 nid=0x6c03 waiting on condition [0x00007f5d79d5f000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000005c3e78330> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:492)
at java.util.concurrent.LinkedBlockingDeque.take(LinkedBlockingDeque.java:680)
at sun.nio.fs.AbstractWatchService.take(AbstractWatchService.java:118)
at org.xnio.nio.WatchServiceFileSystemWatcher.run(WatchServiceFileSystemWatcher.java:85)
at java.lang.Thread.run(Thread.java:745)
Locked ownable synchronizers:
- None
"Thread-93" #133 daemon prio=5 os_prio=0 tid=0x00007f5d8c34d000 nid=0x6c02 runnable [0x00007f5d79e60000]
java.lang.Thread.State: RUNNABLE
at sun.nio.fs.LinuxWatchService.poll(Native Method)
at sun.nio.fs.LinuxWatchService.access$600(LinuxWatchService.java:47)
at sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:314)
at java.lang.Thread.run(Thread.java:745)
Locked ownable synchronizers:
- None
