Re: Getting 404 before the container starts all servlets

2014-01-11 Thread Adrian Tarau
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 en

Re: Getting 404 before the container starts all servlets

2014-01-11 Thread Howard W. Smith, Jr.
On Sat, Jan 11, 2014 at 4:40 AM, 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

Re: Getting 404 before the container starts all servlets

2014-01-11 Thread Mark Thomas
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 o

Re: Getting 404 before the container starts all servlets

2014-01-10 Thread Adrian Tarau
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

RE: Getting 404 before the container starts all servlets

2014-01-10 Thread Caldarale, Charles R
> 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

Re: Getting 404 before the container starts all servlets

2014-01-10 Thread Adrian Tarau
tting 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

RE: Getting 404 before the container starts all servlets

2014-01-09 Thread Caldarale, Charles R
> 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 > p

Getting 404 before the container starts all servlets

2014-01-09 Thread Adrian Tarau
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 config