Mark, Thank you for your response. The same application started under 6.0 does not manifest itself like that.
The first thing that I did was to put a break point in the first filter, to see if the 404 comes from one of the servlets. I got a 404 without reaching any 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 <ma...@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. > > Tomcat doesn't serve *any* requests until everything (including > applications) has started up. bindOnInit only controls when it starts > accepting connections. > > You should only see any response (including 404s) once all the > applications have reported that they have started. > > From what you describe it appears that your application is continuing to > do some initialisation after it has reported it is started. > > Servlets do use lazy init by default but a request to a servlet should > not complete until after the servlet has finished initialising. > > All the indications are that the 404s you are seeing are a result of how > your application is designed. > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
