TheElephantMan
Programmer
Hi, all.
Up here at Acme Widgets, we're using Apache Tomcat as part of a fancy IVR application that sits over our call center. Throughout a typical Production day, one of the log files will occasionally indicate that our IVR application's context is reloading.
Looking through the Tomcat documentation, this seems to be because the reloadable="true" element is set in the <Context> tag in one of the Tomcat configuration files. According to the Tomcat docs, reloadable="true" should only be used in a Development environment, given the high level of system overhead it creates.
As I'm new to this particular application, and the documentation is pretty scant, I'm trying to figure out why we've configured our Production application to run in this fashion. So, here are my questions:
1. What are some drawbacks of changing reloadable from true to false?
2. What might be causing our application to reload itself?
Thanks for the assistance!
TEM
Up here at Acme Widgets, we're using Apache Tomcat as part of a fancy IVR application that sits over our call center. Throughout a typical Production day, one of the log files will occasionally indicate that our IVR application's context is reloading.
Looking through the Tomcat documentation, this seems to be because the reloadable="true" element is set in the <Context> tag in one of the Tomcat configuration files. According to the Tomcat docs, reloadable="true" should only be used in a Development environment, given the high level of system overhead it creates.
As I'm new to this particular application, and the documentation is pretty scant, I'm trying to figure out why we've configured our Production application to run in this fashion. So, here are my questions:
1. What are some drawbacks of changing reloadable from true to false?
2. What might be causing our application to reload itself?
Thanks for the assistance!
TEM