-
Bug
-
Resolution: Obsolete
-
Critical
-
5.4.4
-
Java 8, OSX, Tomcat 7, Derby
-
-
Empty show more show less
-
Basel 35
-
2
I tested our Magnolia 5.4.2 to Magnolia 5.4.4 upgrade, and found something unexpected.
In 5.4.4 you have the option to let Magnolia watch resources (which is the default):
magnolia.resources.classpath.observation.pattern=.*\\.(ftl|yaml)$
However this results in a high use of filedescriptors, around 4500 filedescriptors, which is quite a lot.
I tested the setting which watches 'nothing':
magnolia.resources.classpath.observation.pattern=.*\\.(nonel)$
Which gave a use of around 2000 filedescriptors.
If I want to watch css and js as well (which also live in the resources) like:
magnolia.resources.classpath.observation.pattern=.*\\.(yaml|ftl|css|js)$
Magnolia no longer runs properly and uses close to 10000 filedescriptors which is the default limit on an OSX system.
I can up the limit of course, but the numbers seem quite excessive.
- is related to
-
MGNLEE-414 Stop the installation if the open-files limits are too low
- Closed
- is superseded by
-
MAGNOLIA-6523 Refactor ClasspathResourceOrigin and stabilise its hot resource modification support
- Closed