On Wednesday 08 September 2010 22:49:20 Christopher Schultz wrote:
Rainer,
On 9/3/2010 2:53 AM, Rainer Frey wrote:
And if you use cold deployment only, how do you avoid downtime for other
apps? Do you really use one Tomcat instance per app?
I use one Tomcat instance per webapp, and I
On 09/09/2010 07:10, Rainer Frey wrote:
On Wednesday 08 September 2010 22:49:20 Christopher Schultz wrote:
Rainer,
On 9/3/2010 2:53 AM, Rainer Frey wrote:
And if you use cold deployment only, how do you avoid downtime for other
apps? Do you really use one Tomcat instance per app?
I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 9/3/2010 2:53 AM, Rainer Frey wrote:
And if you use cold deployment only, how do you avoid downtime for other
apps?
Do you really use one Tomcat instance per app?
I use one Tomcat instance per webapp, and I use cold deployment only.
You can create ant task to handle this.
We do it this way.
1. We have cluster on apache2.2 using mod_jk
2. All sessions are sticky but nofailover=off means can migrate to
another server
3. Via jkmanager I disable (activation stopped) 2 out of 3 cluster nodes.
4. Wait for any AJP/HTTP thread
On Monday 30 August 2010 12:55:19 Rainer Frey wrote:
Hi,
It's not normally my style, but is there really no feedback on this topic?
Does anyone use explicit hot deployment with Tomcat Manager in production? How
do you actually upgrade deployed applications?
And if you use cold deployment
Hi,
I just use Tomcat Manager webapp: undeploy and deploy without restarting
Tomcat. It brings no downtime to other webapps/hosts on the same Tomcat,
and downtime of the webapp itself is few seconds per deploy.
This is acceptable for me, since the server load is really low.
If a webapp
Il giorno ven, 03/09/2010 alle 08.53 +0200, Rainer Frey ha scritto:
How
do you actually upgrade deployed applications?
There is a recent thread on this topic, see
http://old.nabble.com/Best-practices-for-deployment-on-cluster-environment-td29532493.html
If you need service continuity, you
