Edoardo Panfili wrote:
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 ?
request at 4:48 PM -> reported an exception via curl
request at 4:50 PM -> reported usually problem via curl
request at 4:51 PM -> reported usually problem via curl
...
the only file modified seems to be manager.2013-10-18.log
-------------------------------------------------------------------------------
ott 18, 2013 4:48:17 PM org.apache.catalina.core.ApplicationContext log
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
at
org.apache.catalina.core.DefaultInstanceManager.checkAccess(DefaultInstanceManager.java:538)
at
org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:511)
at
org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:137)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1144)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:865)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:611)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1023)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
----------------------------------------
There you go, probably.
You are starting Java with the Security Manager on, and the (tomcat)/conf/catalina.policy
contents somehow conflict with what the Manager app is trying to do.
Are you sure that file came from the Tomcat distribution which you are
installing ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
