Hello Ajay,
As per my understanding, the application is using a watch service to monitor directories or changes in a file. In the attached fastThread report, I could see that 42 threads that are related to "Linux Watch Service" are consuming high CPU and all threads are having the same stack trace. This may cause your application to become unresponsive. Can you take a look at the following 2 links:
https://stackoverflow.com/questions/24739280/watchservice-uses-100-of-cpu-on-centos
https://github.com/linkerd/linkerd/issues/391
Here is a stack trace of thread:
stackTrace: 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:748) Locked ownable synchronizers: - None
Edit your Comment