Start connectors after deployment of all webapps have been completed

Hi folks, We are using Embedded Tomcat 7.0.14. We create connectors in the normal way, add the webapps to Tomcat, and then call start on Tomcat. However, we noticed that the connectors get started before the completion of the webapp deployment. Is there a way to delay the starting of the

Re: Start connectors after deployment of all webapps have been completed

have a look at the bindOnInit parameter on the connector http://tomcat.apache.org/tomcat-7.0-doc/config/http.html On 15 mai 2011, at 12:31, Afkham Azeez wrote: Hi folks, We are using Embedded Tomcat 7.0.14. We create connectors in the normal way, add the webapps to Tomcat, and then call

Re: Start connectors after deployment of all webapps have been completed

Thanks Sylvain. That worked. On Sun, May 15, 2011 at 8:21 PM, Sylvain Laurent sylvain.laur...@m4x.orgwrote: have a look at the bindOnInit parameter on the connector http://tomcat.apache.org/tomcat-7.0-doc/config/http.html On 15 mai 2011, at 12:31, Afkham Azeez wrote: Hi folks, We are

Re: Start connectors after deployment of all webapps have been completed

I wanted to express my thanks for the heads-up on bindOnInit as well. I had overlooked that in the connector config doc. Just curious...is there any down side to setting bindOnInit=false? To be honest, tomcat's default behavior of accepting a connection before being able to serve it (i.e. while

Re: Start connectors after deployment of all webapps have been completed

2011/5/16 Dan Checkoway dchecko...@gmail.com: I wanted to express my thanks for the heads-up on bindOnInit as well.  I had overlooked that in the connector config doc. Just curious...is there any down side to setting bindOnInit=false? To be honest, tomcat's default behavior of accepting a