Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4CD1A1A9.9020202@autonomy.com>
Date: Wed, 03 Nov 2010 10:53:45 -0700
From: Kailash Kothari <kailash.kothari@autonomy.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1.14) Gecko/20101006 Lightning/1.0b1 Thunderbird/3.0.9
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Http Coyote connector
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Im using Tomcat 6.0.x (bundled within JBoss)

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?

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

Thanks,
Kailash.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org