Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Edoardo,
On 10/18/13 12:38 PM, Edoardo Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From: edoa...@aspix.it
To: users@tomcat.apache.org Subject: Re: can't connect to
manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to
reproduce the problem on clean Tomcat 7.0.42
install?
the problem was surely present with 7.0.39, the 7.0.42
is a fresh installation for me.
Could you please clarify: does the problem exists on
7.0.42, 7.0.39 or both?
both
Could you provide steps to reproduce the problem on fresh
7.0.42 installation?
- unpack tomcat - modify listen port - modify
tomcat-users.xml - copy jmxremote.access and
jmxremote.password (setting permissions) - build jsvc -
copy configuration files for applications (in
$tomcat/conf/Catalina/localhost)
thank you for you question: also jmx remote access is not
working (in both tomcat 7.0.39 and 7.0.42), maybe the two
problems are related?
I tried to reproduce with the information you provided so
far, but I was unable. It works for me.
Also on my local machine, where jmx is not configured.
Usually, a good place to look first, are the Tomcat
logfiles. What do they say ?
searching for "java.lang.SecurityException: Restricted
(ContainerServlet) class
org.apache.catalina.manager.ManagerServlet"
<MG>my HostManagerServlet is defined in
webapps/host-manager/WEB-INF/web.xml as: <servlet>
<servlet-name>HostManager</servlet-name>
<servlet-class>org.apache.catalina.manager.host.HostManagerServlet</servlet-class>
<init-param>
<param-name>debug</param-name> <param-value>2</param-value>
</init-param> </servlet> <servlet>
<servlet-name>HTMLHostManager</servlet-name>
<servlet-class>org.apache.catalina.manager.host.HTMLHostManagerServlet</servlet-class>
<init-param>
<param-name>debug</param-name> <param-value>2</param-value>
</init-param> </servlet> </MG>
the same for me.
seem that the solution is to add privileged="true"
<MG>my privileged attr in Context is located at
/webapps/host-manager/META-INF/context.xml as: <Context
antiResourceLocking="false" privileged="true" />
also this, the same.
I can try with a new install (as suggested from Ognjen )
then try to use manager before install jsvc and befor setting the
jmx properties.
Neither jsvc nor jmx should have any effect on what you are seeing. I
would like to confirm that, however. Let us know what you discover.
The SecurityException is certainly going to be a problem. It's odd
that you saw the SecurityException which should fail to deploy the
Manager, yet you are seeing the Manager's 404-not-found page which
would require the Manager to be deployed.
The logfile says :
Informazioni: Marking servlet Manager as unavailable
ott 18, 2013 4:48:17 PM org.apache.catalina.core.StandardWrapperValve
invoke
Grave: Allocate exception for servlet Manager
java.lang.SecurityException: Restricted (ContainerServlet) class
org.apache.catalina.manager.ManagerServlet
So to my (admittedly untrained) eyes, it may look like the Manager application (and its
static pages) is deployed, but it is when it's servlet is starting to run that the Java
Security Manager shoots it down..
It doesn't for that undeploy the whole app I guess.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
