[jboss-jira] [JBoss JIRA] Commented: (JBAS-5453) Make DeleteWorkDirOnContextDestroy=true the default setting

Wed Apr 16 05:09:55 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBAS-5453?page=comments#action_12409064 ] 

Remy Maucherat commented on JBAS-5453:
--------------------------------------

The issue you quote is advocating that the opposite default is the best one. Personally, I think it makes more sense in AS to delete the work dir [as AS doesn't have the notion of simple reloads, when something happens with a webapp, it's always undeploy followed by deploy], which was the behavior before it was changed behind my back. Once a final decision is made, feel free to change its value, both have merit (field is o.j.web.tomcat.service.deployers.TomcatDeployer.deleteWorkDirOnContextDestroy).

> Make DeleteWorkDirOnContextDestroy=true the default setting
> -----------------------------------------------------------
>
>                 Key: JBAS-5453
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5453
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.Beta4
>            Reporter: Mike Millson
>         Assigned To: Remy Maucherat
>
> JBAS-3358 added the DeleteWorkDirOnContextDestroy property to handle use cases that require the work directory not be deleted on context destroy. This includes cases where it is desired to persist session data between restarts/redeploys and cases where customers do not precompile JSPs and no not want previously compiled JSPs to be recompiled after a restart/redeploy.
> However, this default setting is causing issues with enterprise users deploying applications that have gone through long quality assurance and user acceptance testing cycles. JSP files will at times necessarily be created earlier than the compilation time of JSPs from older versions of the application that are running in production. Also, sometimes it is necessary to roll back an older version of an application in an emergency. The current default setting causes stale JSPs to be served. 
> Also, enterprise uders often run a clustered configuration, where the concept of saving the session locally in the work directory likely does not apply.
> Precompiling JSPs is ultimately the best solution; however, many users are still not doing this. My guess is there are more users relying on stale JSPs not being served than session persistence across restarts.

-- 
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