Hi!
Have anyone beside me had any issues with the software versions mentioned in
the subject line?
First I thought it was my wacky setup, so I tried to vanilla directly from
tomcat.apache.org, and it still fails.
NOTE : Running the same tomcat installation with JDK1.6.0_12 produces no
2009/6/6 andreas anpa0...@telia.com:
Hi!
Have anyone beside me had any issues with the software versions mentioned in
the subject line?
First I thought it was my wacky setup, so I tried to vanilla directly from
tomcat.apache.org, and it still fails.
NOTE : Running the same tomcat
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Subject: Re: Tomcat 6.0.20, JDK1.6.0_14 and security manager
You may try adding
permission java.lang.RuntimePermission setContextClassLoader;
for the file:${catalina.home}/bin/tomcat-juli.jar
I just verified that does correct
Indeed it does.
But I wonder what this means in terms of security?
I admit that my knowledge of the policy files and security-permissions is very
weak, and granting permissions to something that I do not understand scares me
a bit.
Maybe I should file a bug about this and let it get
2009 21:07:38 +0200
From: anpa0...@telia.com
To: users@tomcat.apache.org
Subject: Re: Tomcat 6.0.20, JDK1.6.0_14 and security manager
Indeed it does.
But I wonder what this means in terms of security?
I admit that my knowledge of the policy files and security-permissions is
very weak
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: Tomcat 6.0.20, JDK1.6.0_14 and security manager
if you can show whats the problem with your policy
check $TOMCAT_HOME/logs/%HOSTNAME%.-MM-DD.log
for details
Since the logging mechanism can't be initialized, there are no log
From: andreas [mailto:anpa0...@telia.com]
Subject: Re: Tomcat 6.0.20, JDK1.6.0_14 and security manager
But I wonder what this means in terms of security?
Konstantin's suggestion should not be a problem. Note that code in Tomcat's
lib directory is given all permissions (by default