You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2012/02/27 04:30:27 UTC

DO NOT REPLY [Bug 52777] New: Automatically shut down old versions in parallel deployment

https://issues.apache.org/bugzilla/show_bug.cgi?id=52777

             Bug #: 52777
           Summary: Automatically shut down old versions in parallel
                    deployment
           Product: Tomcat 7
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: amaniatis@apache.org
    Classification: Unclassified


Under parallel deployment, when an older version in an application has zero
sessions, shut it down automatically to release tomcat and JVM resources.

Christopher Schultz suggested these approaches might be possible (on the Tomcat
user list):

1. Modify the parallel deployment code to register an MBean
NotificationListener that filters for useful events (such as expiring
session notifications on the outgoing webapp).

2. When the listener receives a notification, check the current state
(e.g. session count=0; or, I suppose you could make this a part of
your filter in step #1). If session count = 0, start a new thread that
stops the outgoing webapp and de-registers the listener.

Or.

1. Install a SessionEventListener that counts-down the sessions
(you'll have to get the count from JMX, I suppose) until they equal 0,
then starts a new thread that ... etc.

Or.

1. Install a Timer thread that polls at intervals (1 minute?) to see
if all the sessions are dead and then starts a thread ... etc.

The first idea seems the cleanest, though Tomcat might not actually
fire MBean events for things like session count changing.

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

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


[Bug 52777] Automatically shut down old versions in parallel deployment

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52777

kaosko <ka...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kalle.o.korhonen@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

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


[Bug 52777] Automatically shut down old versions in parallel deployment

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52777

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Mark Thomas <ma...@apache.org> ---
This has been implemented in trunk and 7.0.x and will be included in 7.0.31
onwards. It is optional and controlled by a new attribute (undeployOldVersions)
on the Host.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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


DO NOT REPLY [Bug 52777] Automatically shut down old versions in parallel deployment

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52777

--- Comment #1 from Mark Thomas <ma...@apache.org> 2012-03-20 22:02:02 UTC ---
A variation of the last approach would be to get the auto deployment code to
check the current session count for old context versions and undeploy them once
the count is zero.

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

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