For ServletExec 3.1 or newer:
Across restarts, ServletExec does maintain a record of the last time a JSP was modified. ServletExec accomplishes this by writing a property file to the hard drive.
The name of the file is
Each time SE starts up it compares what's in that file to the JSPs on the hard drive to determine if a JSP will need to be compiled again when requested.
If the JSP is outside a Web App then
jsptimestamps.properties gets placed into the Servlets folder.
If the JSP is inside a Web App then
jsptimestamps.properties gets placed into:
...\ServletExec Data\<SE Virutal Server Name>\<webApp name>\
The default behavior of JSP10Servlet in SE 3.1 and newer is that the init parameter named "compileAfterRestart" is set to false, which means that after SE restarts, it does NOT recompile JSPs unless the requested JSP has a newer timestamp than it did before the SE restart.
If you wish to prevent this behavior and have your JSPs compiled after every SE restart, then pass the JSP10Servlet the init parameter named
"compileAfterRestart" whose value is "true".
For ServletExec 3.0E or older:
Across restarts, ServletExec does not maintain a record of the last time a JSP was modified. Each time ServletExec initializes, it assumes each
requested JSP is new, and therefore re-compiles each JSP the first time it is
requested. At one point it was possible to pass the JSP10Servlet the init
parameter named "compileAfterRestart" with a value of "false" but that
feature was disabled in SE 2.2 due to unwanted side-effects.
As a result, the only way to prevent ServletExec 3.0E or older from compiling JSPs is to pass the JSP10Servlet an init parameter named "compiler" whose value is "none". Of course this will prevent ServletExec from compiling ANY JSPs at all.