On 27/08/2010 12:21, Domenico Briganti wrote: > I've read many response to this thread, but when you redeploy in an > enterprise environment (many httpd+mod_jk -> 4 tomcat server -> a db) > independently if use shared or not appBase, manual or scripted deployer, > with or without tomcat manager, you return to your client at 404 or > worst a 503 when a request reach the tomcat. And for my application it's > not permitted.... > > This is what I think I can do: > Environment (24 Apache+mod_jk -> 4 tomcat server) > mod_jk with ping_mode=A and prepost_timeout=1000 > to redeploy a wabapp: > For each tomcat server: > Connect to JMX MBean and stop AJP connector. > Wait the end of all APJ RequestProcessor. > Redeploy webapp with tomcat manager. > Restart tomcat. > Wait for 60 sec (The default maintenance of mod_jk). > end. > > How about this?
If you're using mod_jk you can enable the /jk-manager worker (restricted to known IPs only, of course) and take the cluster member out of service at the proxy level before disabling the Tomcat. You'll have no downtime and won't drop any connections that way. p > Regards, > Domenico > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
