Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Minhchau DangMinhchau DangReporter
Minhchau DangMinhchau DangBug Type
Regression BugComponents
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Minhchau Dang
Minhchau DangReporter
Minhchau Dang
Minhchau DangBug Type
Regression Bug
Components
Fix versions
Affects versions
Priority
Zendesk Support
Zendesk Support
Zendesk Support
Created November 10, 2011 at 1:04 PM
Updated June 24, 2023 at 3:34 PM
Resolved November 10, 2011 at 1:42 PM
Between Tomcat 6 and Tomcat 7, JSP compilation was updated to allow older JSP files to replace newer JSP files and trigger a recompilation. To do this, the timestamp checking was changed from a lenient check where as long as the .class file is newer than the .jsp file it's treated as up-to-date to a strict check where the .java and .class files will be given the same modified timestamp as the .jsp file.
As a result of this change, build-time JSP precompilation is adding no performance benefit because the .class files currently have a last modified timestamp of the time when they were generated. This means that Tomcat's modified timestamp check fails and Tomcat will try to regenerate the .java and .class files.
To fix this, we'll need to ensure that the timestamp of .class files are the same as the .java and .jsp files when we precompile for Tomcat 7 and above.