Troubleshoot and support > Cache > Dynamic caching in an application
Troubleshoot: Changes to JSP pages have no affect or are not visible
Every time you make changes to a compiled JSP page (for example, myhomePageContent.jsp) the changes do not take affect or are not visible when you load that page. You are finding that the only way for the changes to be visible is to restart the WCS instance.
In order to avoid restarting the instance, reset the "reloadInterval" to a smaller value. Edit the file ibm-web-ext.xml, usually located...
WC_EAR/Stores.war/WEB-INF/ibm-web-ext.xml
Search for "reloadInterval" and reduce its value. Also, ensure that reloadingEnabled="true" is set. You will have to restart the WCS instance, WC_ instance, for the modification to take effect. The value of reloadInterval determines when a thread starts up to check if the JSP source file has changed so that the next time a request comes for that JSP, the new source is compiled. If the interval is too large, the JSP file is not recompiled until the thread starts up again, even though the source has changed and the compiled class is removed. Note that there will be a slight performance impact if you set reloadInterval too low, since the thread will have to check for changes more frequently.
Deploy the updated file using the single file method in the WebSphere administrative console, see Deploy J2EE assets for a single file for more information.