Re: starting connectors after the tomcat startup
Hi Fernando, open HTTP/AJP il the last step that tomcat do when it starts. Why don't you put your initializzations on webapp's context initialize and wait the ready of your resource that? Regards Domenico Il giorno lun, 06/02/2012 alle 21.51 +0530, Pradeep Fernando ha scritto: > Hi all, > > I'm using embedded tomcat within my application. I configured the > org.apache.catalina.startup.Tomcat class using the server.xml found in > tomcat distribution. > But i want to start my connectors after some requirement are met (The > necessary resources being initialized). > > My approach was to set the connector param, > > bindOnInit = "false" > > and then start the connectors at a later stage using connector.start(); > > > but it looks like my connectors are in the "STARTED" life-cycle stage > once i do the Tomcat.start() call. - means they are already started > Am i missing something. How can i achieve my requirement.? > > thanks > --Pradeep > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Best practice to upgrade (redeploy) .war files
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 have to use at least 2 Tomcat instances Regards, Domenico - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Best practices for deployment on cluster environment
Il giorno ven, 27/08/2010 alle 15.36 +0100, Pid ha scritto: > 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. Thank Pid, Yes, I know that. But I have 24 Apache server and more than 200 worker configured. If I can, I prefer to not manage mod_jk too. I will let you know if my system works, Domenco - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Best practices for deployment on cluster environment
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? Regards, Domenico - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: pick load
Il giorno mer, 25/08/2010 alle 15.28 -1000, Alexandre Chapellon ha scritto: > P.S: right now am using ab to send 2000 request with 50 concurrents. What is the report of ab? Domenico - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org