Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
MIME-Version: 1.0
In-Reply-To: <55C47972.8070507@apache.org>
References: 
 <CAAEipQ4_QzG68XDZFt8A4bVv73Y-NtRkPsqOm5R=QZKCgj9Krw@mail.gmail.com>
	<55C47972.8070507@apache.org>
Date: Fri, 7 Aug 2015 11:36:29 +0200
Message-ID: 
 <CAAEipQ7n-7zxjn3zZ4MEk+jO4dNSn8qtgoeZJ68fFwAGGSNHng@mail.gmail.com>
Subject: Re: 404 during application redeploying
From: Pavel Cibulka <pavelcibulka@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a113ddd2ed3ff9b051cb55ed1

--001a113ddd2ed3ff9b051cb55ed1
Content-Type: text/plain; charset=UTF-8

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 <markt@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
>
>

--001a113ddd2ed3ff9b051cb55ed1--