Running Tomcat in development mode in production

[former_member1336901]

Apart from a (tiny) performance impact, are there any reasons for NOT running Tomcat in development mode in production?

It is - unfortunately - sometimes needed that a .jsp or .tag file needs to be fixed at runtime in production. If development mode is switched off, a server restart is required to pick up the changes, otherwise the files are automatically recompiled and reread on the first access after the change.

If development mode is fine in production, how should "modificationTestInterval" and "checkInterval" be set?

https://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html provides some hints, but it does not mention how "checkInterval" should be set.

Any thoughts on this?

[rbespalovnc]

So far I only read about the performance hit. If it isn't bad in your case you can enable it.

First alternative is to set development => true and modificationTestInterval => X. This way you slightly decrease the load after changes in JSP but you can't change them too often. modificationTestInterval means "after the JSP was changed do not check for changes of this JSP in the next X seconds".

Another more sustainable way is to set development => false and checkInterval => Y. This means tomcat will check for a new version of a JSP only once every Y seconds and not on every request.

Graphical comparison:

1. <change>.......<X seconds passed><check><check><check><check><check><change>.....

2. <change>..<Y seconds passed><check>..<Y seconds passed><check>..