You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mi...@deltalloyd.de on 2003/04/07 17:52:44 UTC
problem with java.security.manager and tomcat 4.1.18 as Win2000 service
I tried to start Tomcat 4.1.18 as Win2000 service with the
java.security.manager option.
I've set new JVM Options in the registry.
But every attempt fails with the message:
"java.security.AccessControlException:
access denied (java.util.PropertyPermission catalina.home read)
..."
If I start tomcat with the catalina batch and the same
policy file, every thing works fine.
In the registry the JVM options are identical to the options in the catalina.bat.
I assume if the tomcat can run as service, it can also run with the
java.security.manager as service.
Where is the differecne between executing tomcat in a command line and as service
for the java.security.manager purpose?
Is a special permission needed for the service?
Can it be a problem in the catalina.policy file (every thing is default)?
Thanks in advance
Michael Uhlig
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org