Konstantin,Thanks this has fixed it for me.
> > I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50.
> > After upgrading I got lots of the below errors recorded in catalina.out
> > The errors are not logged if I disable tldValidation (either by settings
> > tldValidation=false in cont
> Date: Wed, 22 Jan 2014 15:15:53 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 7.0.50 tldValidation
>
> On 22/01/2014 14:12, Paul Beckett wrote:
> > Does anyone know:
> - Why this occurs only since 7.0.50
> Changes to XML v
> I can't tell how much easier it is to manage Tomcat installations
> (even small ones) with these two separated: Tomcat base install goes
> one place, your configuration and everything you need goes another.
> Upgrades are as simply as changing the CATALINA_HOME path, and
> downgrades (if necessar
my ignorance in
this area).
Thanks again,Paul
> Date: Wed, 22 Jan 2014 10:24:20 -0500
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 7.0.50 tldValidation
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On
I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50.
After upgrading I got lots of the below errors recorded in catalina.out
The errors are not logged if I disable tldValidation (either by settings
tldValidation=false in context.xml or removing the CATALINA_OPTS property:
org.apache.
I would second reading the Tomcat security how-to. The OWASP guide to securing
tomcat : https://www.owasp.org/index.php/Securing_tomcat is also worth a look.
You could also consider starting tomcat with the security manager enabled...
although intially finding and configuring all the permissions
