.jsp fails to recompile after redeployment ------------------------------------------ Key: JBAS-5282 URL: http://jira.jboss.com/jira/browse/JBAS-5282 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, JBossAS-3.2.6 Final, JBossAS-5.0.0.Beta1, JBossAS-4.0.2 Final, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.GA, JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1RC1, JBossAS-3.2.8RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1, Closed issues from sourceforge, JBossAS-4.0.3RC2, JBossAS-4.0.4RC1, JBossAS-4.0.3 Final, No Release, JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP2, JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: all Reporter: Thomas Bosch Fix For: JBossAS-4.0.4.CR2 When redeploying a .ear or .war containing .jsps, there are many situations causing a .jsp that needs to be recompiled to not be recompiled, or to be recompiled continuously. Any situation causing the timestamp of the modified .jsp to be older than the timestamp of its compiled class will cause it not to be recompiled; for example: - reverting to a previous version of the .jsp using a version control - timezone difference between development and production server - .jsp never visited in production server until after change is made, which can happen for a rarely visited page, or a newly deployed server. Continuous recompilation happens in any situation causing the timestamp of the modified .jsp to be newer than the current time, and will happen until current time catches up; for example: - timezone difference between development and production server - future time assigned to .jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira