Il 18/10/13 18:25, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 18:16, Caldarale, Charles R ha scritto:
From: Edoardo Panfili [mailto:edoa...@aspix.it]
Subject: Re: can't connect to manager application
seem that the solution is to add privileged="true" at
$tomcat/conf/context.xml... and the "reoload" command now works.
You really, really, really must not do that. Adding
privileged="true" to conf/context.xml makes _all_ deployed webapps
privileged. The <Context> element for the manager webapp already has
privileged="true" in it - unless you took it out.
ok, it look not so good for me to change default privileges.
but.. what can I do?
Note that if you're using a 3rd-party repackaged version of Tomcat,
all bets are off. The repackagers frequently make a mess of things,
such as the above. Best to use a Tomcat downloaded from
tomcat.apache.org.
I use the tar.gz from tomcat.apche.org.
It could be that there is an error in the catalina.policy file of the
standard distribution.
maybe, but an error from my side is more probable!
Many people do not run with the Java Security Manager enabled, so it may
have been unnoticed until now.
removing my setenv.sh this is the command that starts tomcat (from ps)
jsvc.exec -java-home /usr/lib/jvm/java-6-openjdk/ -user tomcat -pidfile
/usr/local/tomcat7/logs/catalina-daemon.pid -wait 10 -outfile
/usr/local/tomcat7/logs/catalina-daemon.out -errfile &1 -classpath
/usr/local/tomcat7/bin/bootstrap.jar:/usr/local/tomcat7/bin/commons-daemon.jar:/usr/local/tomcat7/bin/tomcat-juli.jar
-Djava.util.logging.config.file=/usr/local/tomcat7/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.endorsed.dirs= -Dcatalina.base=/usr/local/tomcat7
-Dcatalina.home=/usr/local/tomcat7
-Djava.io.tmpdir=/usr/local/tomcat7/temp
org.apache.catalina.startup.Bootstrap
using my setenv.sh
jsvc.exec -java-home /usr/local/jdk1.7.0_40 -user tomcat -pidfile
/usr/local/tomcat7/logs/catalina-daemon.pid -wait 10 -outfile
/usr/local/tomcat7/logs/catalina-daemon.out -errfile &1 -classpath
/usr/local/tomcat7/bin/bootstrap.jar:/usr/local/tomcat7/bin/commons-daemon.jar:/usr/local/tomcat7/bin/tomcat-juli.jar
-Djava.util.logging.config.file=/usr/local/tomcat7/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Xmx8192m -Xms2048m -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1707
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=/usr/local/tomcat7/conf/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=/usr/local/tomcat7/conf/jmxremote.access
-Djava.endorsed.dirs= -Dcatalina.base=/usr/local/tomcat7
-Dcatalina.home=/usr/local/tomcat7
-Djava.io.tmpdir=/usr/local/tomcat7/temp
org.apache.catalina.startup.Bootstrap
but in both the situations "reload" does not works.
Or else, you are running a newer version of Tomcat with an older version
of this file.
I recheck my "Tomcat update todo list", catalina.policy is not moved.
Edoardo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
