tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Http Coyote connector
Date Thu, 11 Nov 2010 19:43:50 GMT
Hash: SHA1


On 11/3/2010 1:53 PM, Kailash Kothari wrote:
> I understand that the Http Coyote connector that binds port 8080 on the
> OS is started right at the end in the tomcat startup process after all
> webapps have been deployed.
> This is a problem for us because we have one webapp that is deployed
> first and then a second webapp that needs to talk to the first webapp in
> a startup servlet.
> Since the http connector hasn't been started, the webapps cant talk to
> each other until the server has started up completely.
> Is there a design reason that the http connector is started at the end
> of boot up rather than earlier?

My guess is that it doesn't make any sense to accept requests from
clients before the services are actually available.

As I see it, you have several options:

* Run your webapps in different Tomcat instances, and start them up in
the order you prefer.

* Change your webapps so that they can communicate lazily with each
other instead of immediately upon deployment. This allows you to keep
the existing startup semantics but let your webapps communicate

* Modify Tomcat to start the connectors first and then the webapps.
Understand that you might get some 404s or other weird errors during
webapp deployment.

> I tweaked the source code to start this up earlier and have everything
> working as I need, but could this have any side effects?

I'm sure it could have some side effects... what they are I couldn't
guess. Good advice in all environments: test, test, test.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message