Re: Getting 404 before the container starts all servlets
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 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
Re: Getting 404 before the container starts all servlets
I tried with 7.0.47 and I still get 404 regardless of the the state of bindOnInit. // On 01/10/2014 01:38 PM, Caldarale, Charles R wrote: From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org] Subject: Re: Getting 404 before the container starts all servlets I tried with bindOnInit=false and bindOnInit=true, it makes no difference. I'm using tomcat 7.0.34, would this option be available in 7.0.34? It should be. Note that the Tomcat you're using is over a year old, so you might want to consider upgrading, regardless. Lots of things fixed since then. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Getting 404 before the container starts all servlets
I tried with bindOnInit=false and bindOnInit=true, it makes no difference. I'm using tomcat 7.0.34, would this option be available in 7.0.34? Thanks, Adrian Tarau. On 01/09/2014 11:19 PM, Caldarale, Charles R wrote: From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org] Subject: Getting 404 before the container starts all servlets After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all servlet are initialized, which is not what you would expect. Is this behavior normal for 7.X? Is there a way to configure 7.x to behave like 6.x? Look at the bindOnInit attribute for elements: http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard_Implementation But be aware of the side effects as discussed in these threads: http://marc.info/?l=tomcat-user&m=136386106909331&w=2 http://marc.info/?l=tomcat-user&m=130549517506701&w=2 - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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
Getting 404 before the container starts all servlets
Hello, After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all servlet are initialized, which is not what you would expect. Is this behavior normal for 7.X? Is there a way to configure 7.x to behave like 6.x? Thank you, Adrian Tarau. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
