You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Pavel Cibulka <pa...@gmail.com> on 2015/08/07 11:00:57 UTC
404 during application redeploying
Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application
(by replacing WAR file), tomcat returns 404 for short period of time. Is
this intended?
I have found in:
https://bz.apache.org/bugzilla/show_bug.cgi?id=53024
Bug 53024 - Accessing Servlet while Reloading context gives 404 error
Mark Thomas 2012-05-08 19:08:09 UTC
"Thanks for the test case. This has been fixed in trunk and 7.0.x and will
be included in 7.0.28 onwards.
I also took the opportunity to improve the handling when a watched resource
(such as web.xml) changes. This is now handled with a reload (so no 404s)
rather than stop followed by a start."
It seems to me, that Tomcat should pause requests on redeploy instead of
returning 404. Or does this works differently for WAR files?
Thanks,
Pavel Cibulka
Re: 404 during application redeploying
Posted by Pavel Cibulka <pa...@gmail.com>.
redeploy != reload
I see now. External context.xml seems good to me.
Thanks for help.
Pavel Cibulka
On Fri, Aug 7, 2015 at 11:25 AM, Mark Thomas <ma...@apache.org> wrote:
> On 07/08/2015 10:00, Pavel Cibulka wrote:
> > Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application
> > (by replacing WAR file), tomcat returns 404 for short period of time. Is
> > this intended?
>
> Yes.
>
> > I have found in:
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=53024
> > Bug 53024 - Accessing Servlet while Reloading context gives 404 error
> > Mark Thomas 2012-05-08 19:08:09 UTC
> > "Thanks for the test case. This has been fixed in trunk and 7.0.x and
> will
> > be included in 7.0.28 onwards.
> > I also took the opportunity to improve the handling when a watched
> resource
> > (such as web.xml) changes. This is now handled with a reload (so no 404s)
> > rather than stop followed by a start."
> >
> > It seems to me, that Tomcat should pause requests on redeploy instead of
> > returning 404. Or does this works differently for WAR files?
>
> It depends.
>
> redeploy != reload and which you get depends on circumstances. I
> strongly recommend that you read this page:
> http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html
>
> There are a number of ways you could get the reload behaviour you want.
>
> 1. Use an external context.xml file. Updates to the WAR would then only
> result in a reload.
>
> 2. Use parallel deployment
>
>
> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment
>
> HTH,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: 404 during application redeploying
Posted by Mark Thomas <ma...@apache.org>.
On 07/08/2015 10:00, Pavel Cibulka wrote:
> Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application
> (by replacing WAR file), tomcat returns 404 for short period of time. Is
> this intended?
Yes.
> I have found in:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=53024
> Bug 53024 - Accessing Servlet while Reloading context gives 404 error
> Mark Thomas 2012-05-08 19:08:09 UTC
> "Thanks for the test case. This has been fixed in trunk and 7.0.x and will
> be included in 7.0.28 onwards.
> I also took the opportunity to improve the handling when a watched resource
> (such as web.xml) changes. This is now handled with a reload (so no 404s)
> rather than stop followed by a start."
>
> It seems to me, that Tomcat should pause requests on redeploy instead of
> returning 404. Or does this works differently for WAR files?
It depends.
redeploy != reload and which you get depends on circumstances. I
strongly recommend that you read this page:
http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html
There are a number of ways you could get the reload behaviour you want.
1. Use an external context.xml file. Updates to the WAR would then only
result in a reload.
2. Use parallel deployment
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment
HTH,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org