Sounds like your /etc/init.d/tomcat5 startup script is doing more than
the standard service start script. Take a look at it for the security
options as well as maybe reading/copying config files from some where
else. Is you server set to run under high security?
--David
tukutela wrote:
For
A script in /etc is not the standard method to start tomcat. I'd guess
you're using debian, and used apt-get install tomcat? It sets up
several non-standard options, like enabling the security manager by
default. Either edit the /etc/init.d/tomcat5 script (it says where to
change it to turn
For testing at least, how can I turn the security manager off?
I haven't used catalina.sh start -security
I use the standard /etc/init.d/tomcat5 start method
Also, I've added the grant permissions to the catalina.policy file, but
every time I start up tomcat the file reverts to its standard and
You are running tomcat with the security manager enabled. You'll have
to update catalina.policy to allow the connection.
--David
tukutela wrote:
Hi guru's, some serious help needed.
I've been running a development environment on my laptop for the last few
weeks, and now the product is finis
