Some app servers like Weblogic offer you features like dynamic deployment, where the server keeps "old" version of your webapp around servicing existing clients and any new client comming will be automatically logged in into "new" version. Once all the sessions are expired on the "old" version it will finally remove it. This way you can achieve seamless redeployment without a single second of downtime, but you application have to be specially coded for this (e.g. if you want to update DB schema, you would have to be vary careful and only add the things, but not remove, etc.). Anyway this kind of approach will not work here either since you have exclusive lock on your repository and there is no way to run two copies of the webapp connected to the same repo (plus the app server like WLS is bit higher on the price scale then Tomcat)
On the other hand in normal EE deployment scenario, you have 2+ public instances, so it should not be a big problem to put one down for few minutes it takes to bring it to new version, and once it is up, update the other public instances same way. Agreed, if you push content to public as often as every few minutes, you would need the activation queue for this to be completely painless procedure. Jan On Mon, 2009-03-30 at 13:56 +0200, Grégory Joseph wrote: > Hi Matteo, > > Unfortunately, that button won't help; it will only re-extract the > files, like Vasko said. And it might even put your module at stake, > given that it will not update, for instance, the version number under / > modules/x. Note that you don't have to restart Tomcat completely; if > you use tomcat's manager or host-manager app, you can selectively > restart one webapp or virtual host. (Although I wouldn't recommend > doing it on the long run; things (typically jsp) seem to be leaking a > little...) > > -g > > > On Mar 30, 2009, at 12:53 PM, Matteo Pelucco wrote: > > > > > Hi all, > > a little question. > > > > Nowadays, every time we release a new module / module update we > > restart tomcat. > > > > Sometimes the updates are minimal (e.g.: bug fix over a class, new > > method on a bean..). Is it possible to deploy the update module > > without restarting tomcat? > > > > I saw the "redeploy" button under Tools -> Deployment, that button > > can help? > > > > Matteo > > > > > > ---------------------------------------------------------------- > > For list details see > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: <[email protected]> > > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- -- Best regards, Jan Haderka Magnolia International Ltd. ---------------------------------------------------------------------- [email protected] http://www.magnolia-cms.com Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
