tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38975] New: - manager-undeploy unconditionally deletes serialized session state
Date Wed, 15 Mar 2006 08:44:17 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38975>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38975

           Summary: manager-undeploy unconditionally deletes serialized
                    session state
           Product: Tomcat 5
           Version: 5.5.15
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rm@moosauer.de


Until 5.5.9 it was possible to update a webapp via manager undeploy/deploy
without interrupting user sessions.
It made a very smooth user experience possible with quick updates and high
availability.
This is no more possible now with WAR-deployment.

Now, a undeploy _always_ removes the work-directory for that context
and SESSIONS.ser with it. A deploy/update does the same.
I know that this behavior was introduced because outdated files in the
work-directory can cause problems with a changed application. And I know
that this kind of problems is not what we want.

But the bad thing is:
It cannot be turned off or otherwise be circumvented. 

Consider a nearly-productive web-application which is quite stable and only
minor bugfixes have to be done. But the application is in use and a
number of users are continously logged on and working.
These minor bug fixes are happening quite often and they _always_ compatible
with the serialized session state.

I would like to request an enhancement the manager or the container itself to
control this behavior. What I suggest, is some kind of 'soft' re-deploy without
removing the session state.

I discussed this on the users-list recently and 
the problem seems to be not exactly trival. I know that the deletion of the work
directory is not done in the manager but in the container. As a result, it's not
so easy to manipulate the behavior.

A good solution could be:
Manager has a new attribute 'update' to the deploy-task. Maybe we can 
use this one, the initiate a soft re-deploy. 
Still better maybe an attribute 'keepSessions' to the undeploy-task. This one
would be clearly say what it does. And it could be 'false' by default to be sure.

Developers who are more familiar with tomcat's interna may have much better
suggestions. Please let me know! I would appreciate to help implementing this.

All other please vote for this enhancement because we have lost a very nice 
feature here.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message