Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Obsolete
Priority: Major
Fix Version/s: TBD EAP 5
Affects Version/s: EAP_EWP 5.1.2
Component/s: Web
Labels:
None
Environment:

all

Workaround:

Workaround Exists
Workaround Description:

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
Estimated Difficulty:
Low
Release Note Text:

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>.
Release Note Status:
Documented as Known Issue
Docs QE Status:
NEW
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1136170

Description

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.

Attachments

Issue Links

is cloned by

JBAS-5282 .jsp fails to recompile after redeployment

Closed

Activity

People

Assignee:: Remy Maucherat

Reporter:: Lami Akagwu

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 2012/03/06 9:54 AM

Updated:: 2022/09/09 6:11 AM

Resolved:: 2019/05/21 4:50 AM

Time Tracking

Estimated:

Remaining:

Logged:

Not Specified