-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 10/28/2011 5:20 PM, Mark Thomas wrote:
And the code says...?
Knowing that you'd say that, I had started looking for the code.
Unfortunately it's hard to search through 1200 source files for the
place where a Context is instantiated using
2011/11/1 Christopher Schultz ch...@christopherschultz.net:
I'm having trouble locating the code that auto-undeploys old versions
when all sessions have expired.
There is no such code in Tomcat.
You will see in the manager app that the counter of sessions is zero,
but there is no such feature
On 31/10/2011 20:22, Konstantin Kolinko wrote:
2011/11/1 Christopher Schultz ch...@christopherschultz.net:
I'm having trouble locating the code that auto-undeploys old versions
when all sessions have expired.
There is no such code in Tomcat.
You will see in the manager app that the
Hi Chris,
But how would it cause an outage? ROOT##003 would not necessarily be
copied from the file ROOT##001.war
It'll be a separate deployment, but just using the same build that got
deployed as ROOT##001.
Whether ROOT##001 is marked for undeployment should not make a
difference to ROOT##003.
From: Ellecer Valencia [mailto:elle...@gmail.com]
Subject: Re: Rollback in Tomcat7 under parallel deployment
But how would it cause an outage? ROOT##003 would not necessarily be
copied from the file ROOT##001.war
I believe Chris was referring to your originally stated tactic of just
Ah yes. Thanks Chuck. That makes more sense. =)
On Mon, Oct 31, 2011 at 3:04 PM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: Ellecer Valencia [mailto:elle...@gmail.com]
Subject: Re: Rollback in Tomcat7 under parallel deployment
But how would it cause an outage? ROOT##003
Also, what happens if ROOT##001 and ##002 have the same log4j configs
and are writing to the same log file?? How have people handled this
situation?
You'll certainly end up with both apps writing to the same file. Whether
or not that is a problem will depend on exactly how you have
On 29/10/2011 12:41, chris derham wrote:
Also, what happens if ROOT##001 and ##002 have the same log4j configs
and are writing to the same log file?? How have people handled this
situation?
You'll certainly end up with both apps writing to the same file. Whether
or not that is a problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ellecer,
On 10/27/2011 7:11 PM, Ellecer Valencia wrote:
On Thursday, October 27, 2011, Mark Thomas ma...@apache.org
wrote:
A better way to handle the rollback scenario is to deploy a copy
of ROOT##001.war as ROOT#003.war.
That's the first
On 28/10/2011 21:53, Christopher Schultz wrote:
Ellecer,
On 10/27/2011 7:11 PM, Ellecer Valencia wrote:
On Thursday, October 27, 2011, Mark Thomas ma...@apache.org
wrote:
A better way to handle the rollback scenario is to deploy a
copy of ROOT##001.war as ROOT#003.war.
That's the first
Hi,
If I'm using parallel deployment in Tomcat 7, and now have 2 webapps
/webapps/ROOT##001.war
/webapps/ROOT##002.war
and then get problems in the new version and want to rollback to ROOT##001.war.
If I delete the more recent version by doing
rm /tomcat/webapps/ROOT##002.war
What happens to
On 27/10/2011 07:41, Ellecer Valencia wrote:
Hi,
If I'm using parallel deployment in Tomcat 7, and now have 2 webapps
/webapps/ROOT##001.war
/webapps/ROOT##002.war
and then get problems in the new version and want to rollback to
ROOT##001.war.
If I delete the more recent version by
On Thursday, October 27, 2011, Mark Thomas ma...@apache.org wrote:
Also, what happens if ROOT##001 and ##002 have the same log4j configs
and are writing to the same log file?? How have people handled this
situation?
You'll certainly end up with both apps writing to the same file. Whether
or
13 matches
Mail list logo
