This appears to be another variant of the following bug that was supposed to
be fixed in 7.0.26.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52591
--
View this message in context:
http://tomcat.10.n6.nabble.com/Problem-with-JMXProxy-after-upgrading-from-6-0-29-to-7-0-26-tp4551753p4551993
Hi,
We have been using the following two JMXProxy URLs for monitoring without
issue in 6.0.29.
http://localhost:8080/manager/jmxproxy/?qry=*:type=Executor,name=tomcatThreadPool
OK - Number of results: 1
Name: Catalina:type=Executor,name=tomcatThreadPool
modelerType: org.apache.tomcat.util.