Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8362

.jsp fails to recompile after context redeployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • TBD EAP 5
    • EAP_EWP 5.1.2
    • Web
    • None

    • all

    • Workaround Exists
    • Hide

      Set deleteWorkDirOnContextDestroy to true in $JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml

      Show
      Set deleteWorkDirOnContextDestroy to true in $JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
    • Low
    • Hide
      When trying to redeploying an EAR or WAR containing JSPs, there are instances which cause the JSP to either not be recompiled, or to be recompiled continuously. For example, if the timestamp of the modified JSP is older than the timestamp of its compiled class, it will not be recompiled. Examples of how this might occur include: reverting to a previous version of the .jsp using a version control, timezone difference between development and production server or the JSP never haveing been visited on a production server until after change is made.

      This is normal behaviour on JBoss Enterprise Application Platform but a workaround is available. Set the parameter <parameter>deleteWorkDirOnContextDestroy</parameter> to <value>true</value> in <filename>$JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml</filename>.
      Show
      When trying to redeploying an EAR or WAR containing JSPs, there are instances which cause the JSP to either not be recompiled, or to be recompiled continuously. For example, if the timestamp of the modified JSP is older than the timestamp of its compiled class, it will not be recompiled. Examples of how this might occur include: reverting to a previous version of the .jsp using a version control, timezone difference between development and production server or the JSP never haveing been visited on a production server until after change is made. This is normal behaviour on JBoss Enterprise Application Platform but a workaround is available. Set the parameter <parameter>deleteWorkDirOnContextDestroy</parameter> to <value>true</value> in <filename>$JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml</filename>.
    • Documented as Known Issue
    • NEW

      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.

              rmaucher Remy Maucherat
              rhn-support-lakagwu Lami Akagwu
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified