Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
References: <52CF5B15.3060303@adrian.tarau.org>
 <99C8B2929B39C24493377AC7A121E21FC5D16A6A03@USEA-EXCH8.na.uis.unisys.com>
 <52D02FEE.6060709@adrian.tarau.org>
 <99C8B2929B39C24493377AC7A121E21FC5D173AB63@USEA-EXCH8.na.uis.unisys.com>
 <52D07D5B.3020807@adrian.tarau.org> <52D11184.3050305@apache.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <52D11184.3050305@apache.org>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <A08A6F18-DD6D-48D2-A60E-98AB72D63051@adrian.tarau.org>
Cc: Tomcat Users List <users@tomcat.apache.org>
From: Adrian Tarau <mailinglist@adrian.tarau.org>
Subject: Re: Getting 404 before the container starts all servlets
Date: Sat, 11 Jan 2014 16:58:17 -0500
To: Tomcat Users List <users@tomcat.apache.org>

Mark,

Thank you for your response. The same application started under 6.0 does not=
 manifest itself like that.=20

The first thing that I did was to put a break point in the first filter, to s=
ee if the 404 comes from one of the servlets. I got a 404 without reaching a=
ny the break point.

I will enable debugging in Tomcat and come back with additional information.=
 I do not exclude an application issue, however, everything points to Tomcat=
 at this point.

Sent from my iPhone

On Jan 11, 2014, at 4:40, Mark Thomas <markt@apache.org> wrote:

> On 10/01/2014 23:08, Adrian Tarau wrote:
>> I tried with 7.0.47 and I still get 404 regardless of the the state of
>> bindOnInit.
>=20
> Tomcat doesn't serve *any* requests until everything (including
> applications) has started up. bindOnInit only controls when it starts
> accepting connections.
>=20
> You should only see any response (including 404s) once all the
> applications have reported that they have started.
>=20
> =46rom what you describe it appears that your application is continuing to=

> do some initialisation after it has reported it is started.
>=20
> Servlets do use lazy init by default but a request to a servlet should
> not complete until after the servlet has finished initialising.
>=20
> All the indications are that the 404s you are seeing are a result of how
> your application is designed.
>=20
> Mark
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>=20

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