WildFly 8.2.0.Final use of inotify watches

[fmr]

Hello,

We recently upgraded from JBoss AS 7.1.1 to WildFly 8.2.0 and since then we have been facing issue related with the limit of inotify watches.

First we hit the limit for notify instances, we could verify that the WildFly process had around 300 instances which seem to be one for each deployed application.

After raising the limit of the notify instances we eventually hit the limit of the inotify watches. We raised the limit to half a million which solved the problem.

However we are not able to correctly size the limit of inotify watches, as far as I can tell there is no way to count the number of notify watches open at any given time.

We never had this issue in JBoss AS 7.1.1, I can only guess that WildFly started to make use of the inotify infrastructure introduced in Java 7.

Is there any way to properly size the limit of inotify watches?

For example is there a way to determine the limit based on the number of applications deployed, the number of jar in each application, etc...

Thank you for your help,

Best Regards,

Filipe Rodrigues

[ctomc]

Upgrade to WildFly 9 or disable hot deployment (deployment-scanner subsystem) and deploy via admin console / cli

[fmr]

Hello Tomaz,

Thank you for your reply.

I tried disabling the hot deployment by removing the deployment-scanner subsystem tags from standalone.xml and respective extension, then I restarted the server.

Is this the correct procedure?

I noticed that there is one thread named "xnio-file-watcher" per deployed application.

Are these threads related with hot deployment?

Shouldn't these threads stop being created if I disabled the hot deployment?

Thank you for your help,

Best Regards,

Filipe Rodrigues