Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4CD19EBF.60108@apache.org>
Date: Wed, 03 Nov 2010 13:41:19 -0400
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Http Coyote Connector
References: <4CD19A8F.3040401@autonomy.com>
In-Reply-To: <4CD19A8F.3040401@autonomy.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 03/11/2010 13:23, Kailash Kothari wrote:
> 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?

This belongs on the users list.

Mark


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