You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Albert Kam <mo...@gmail.com> on 2013/11/02 15:42:16 UTC
How to force undeployOldVersions ?
I have had a good experience doing the parallel deployment with the latest
stable build of tomcat7, by using autoDeploy after copying a newer version
of WAR to the appbase. As i can see from my manager app, there are 2
versions running, the newer one is serving new requests as expected.
The problem is that, although with undeployOldVersions=true, the old
version of the webapp is still there.
>From what i've seen from catalina.out, there's a ThreadLocal issues that
are being used by 3rd party classes and i assumes this is the output of the
undeployment process failing.
Is there a way that i can 'force' the undeployOldVersions ?
I've thought about using ant task to undeploy, but it seems that i cannot
specify the version to undeploy.
--
Do not pursue the past. Do not lose yourself in the future.
The past no longer is. The future has not yet come.
Looking deeply at life as it is in the very here and now,
the practitioner dwells in stability and freedom.
(Thich Nhat Hanh)
Re: How to force undeployOldVersions ?
Posted by Albert Kam <mo...@gmail.com>.
My apologies. My assumption was wrong about using the latest stable build.
My debian wheezy's version on tomcat7 package is 7.0.28-4.
I wonder how do i upgrade to the latest version without sacrificing all the
good stuffs already provided in wheezy,
maybe something like updating tomcat's jars ? Is it a bad idea ?
Thanks for pointing this out, really appreciate it !
On Sat, Nov 2, 2013 at 11:50 PM, Konstantin Kolinko
<kn...@gmail.com>wrote:
> 2013/11/2 Albert Kam <mo...@gmail.com>:
> > Hello. I forgot to mention that i've made sure from manager app that the
> > old webapp has 0 sessions, so i think this should have triggered the
> > undeploying process.
> >
> > Here's my host's attributes :
> > <Host name="localhost" appBase="webapps"
> > unpackWARs="true" autoDeploy="true"
> undeployOldVersions="true">
> >
> > And i've just done some greps on catalina.out, and i got this related
> > output :
> > WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> > 'undeployOldVersions' to 'true' did not find a matching property.
> >
> > I've seen that in the onfig it's indeed undeployOldVersions, and the
> value
> > of true is also fine.
> > I wonder what might be the cause of the warning.
> >
> > I'm using debian wheezy's tomcat7 packages.
> >
>
> 3-rd party packages are usually rather old. Looking at that error
> message it seems that yours does not have this feature.
>
> What x.y.z version of Tomcat is that?
>
> You need Tomcat 7.0.32 or later.
> http://tomcat.apache.org/oldnews-2012.html#Tomcat_7.0.32_Released
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
--
Do not pursue the past. Do not lose yourself in the future.
The past no longer is. The future has not yet come.
Looking deeply at life as it is in the very here and now,
the practitioner dwells in stability and freedom.
(Thich Nhat Hanh)
Re: How to force undeployOldVersions ?
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/11/2 Albert Kam <mo...@gmail.com>:
> Hello. I forgot to mention that i've made sure from manager app that the
> old webapp has 0 sessions, so i think this should have triggered the
> undeploying process.
>
> Here's my host's attributes :
> <Host name="localhost" appBase="webapps"
> unpackWARs="true" autoDeploy="true" undeployOldVersions="true">
>
> And i've just done some greps on catalina.out, and i got this related
> output :
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'undeployOldVersions' to 'true' did not find a matching property.
>
> I've seen that in the onfig it's indeed undeployOldVersions, and the value
> of true is also fine.
> I wonder what might be the cause of the warning.
>
> I'm using debian wheezy's tomcat7 packages.
>
3-rd party packages are usually rather old. Looking at that error
message it seems that yours does not have this feature.
What x.y.z version of Tomcat is that?
You need Tomcat 7.0.32 or later.
http://tomcat.apache.org/oldnews-2012.html#Tomcat_7.0.32_Released
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to force undeployOldVersions ?
Posted by Albert Kam <mo...@gmail.com>.
Hello. I forgot to mention that i've made sure from manager app that the
old webapp has 0 sessions, so i think this should have triggered the
undeploying process.
Here's my host's attributes :
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true" undeployOldVersions="true">
And i've just done some greps on catalina.out, and i got this related
output :
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
'undeployOldVersions' to 'true' did not find a matching property.
I've seen that in the onfig it's indeed undeployOldVersions, and the value
of true is also fine.
I wonder what might be the cause of the warning.
I'm using debian wheezy's tomcat7 packages.
On Sat, Nov 2, 2013 at 9:42 PM, Albert Kam <mo...@gmail.com> wrote:
> I have had a good experience doing the parallel deployment with the latest
> stable build of tomcat7, by using autoDeploy after copying a newer version
> of WAR to the appbase. As i can see from my manager app, there are 2
> versions running, the newer one is serving new requests as expected.
>
> The problem is that, although with undeployOldVersions=true, the old
> version of the webapp is still there.
> From what i've seen from catalina.out, there's a ThreadLocal issues that
> are being used by 3rd party classes and i assumes this is the output of the
> undeployment process failing.
>
> Is there a way that i can 'force' the undeployOldVersions ?
> I've thought about using ant task to undeploy, but it seems that i cannot
> specify the version to undeploy.
>
> --
> Do not pursue the past. Do not lose yourself in the future.
> The past no longer is. The future has not yet come.
> Looking deeply at life as it is in the very here and now,
> the practitioner dwells in stability and freedom.
> (Thich Nhat Hanh)
>
--
Do not pursue the past. Do not lose yourself in the future.
The past no longer is. The future has not yet come.
Looking deeply at life as it is in the very here and now,
the practitioner dwells in stability and freedom.
(Thich Nhat Hanh)