XSLweb scans all web applications for a webapp.xml file that has changed after launch. Such a change triggers XSlweb to restart the webapp in accordance with the new settings.
This scan seems to include all files and folders within all web applications, while this could confined to the root of all web application folders (where a webapp.xml is expected to occur).
/home/webapps/app1/webapp.xml
/home/webapps/app2/webapp.xml
...and so on
The scan turns out to be inefficient (taking up an overhead of CPU every 3 seconds) especially when a lot of (static) files are part of the web application. Many static files should be avoided, but may under circumstances be required. For example, a PNG flag for all countries of the world may be integral part of the application, rather than "data".
Request to change the operation to be confined to the root of any web application folder.
XSLweb scans all web applications for a
webapp.xmlfile that has changed after launch. Such a change triggers XSlweb to restart the webapp in accordance with the new settings.This scan seems to include all files and folders within all web applications, while this could confined to the root of all web application folders (where a webapp.xml is expected to occur).
The scan turns out to be inefficient (taking up an overhead of CPU every 3 seconds) especially when a lot of (static) files are part of the web application. Many static files should be avoided, but may under circumstances be required. For example, a PNG flag for all countries of the world may be integral part of the application, rather than "data".
Request to change the operation to be confined to the root of any web application folder.