Bug 65404 - after upgrade Tomcat 8.5.57 to 8.5.66 the Tomcat Manager Status page is unstable
Summary: after upgrade Tomcat 8.5.57 to 8.5.66 the Tomcat Manager Status page is unstable
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Manager (show other bugs)
Version: 8.5.66
Hardware: PC All
: P2 normal (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2021-06-28 14:53 UTC by Jordan
Modified: 2021-06-28 16:33 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Jordan 2021-06-28 14:53:40 UTC
Unfortunately we use an APM that relies on the Tomcat Manager Status page.

This was working fine with Tomcat 8.5.57

Since upgrading to Tomcat 8.5.66 the Status page has become unstable.

After some time (could be a couple hours, could be days) it will eventually start missing the info at the bottom of the page and an error will be logged:

22-Jun-2021 13:34:26.736 SEVERE [http-nio-8080-exec-7] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [Status] in context with path [/manager] threw exception [javax.management.AttributeNotFoundException: Cannot find attribute maxTime for BaseModelMbean[null]] with root cause
           javax.management.AttributeNotFoundException: Cannot find attribute maxTime for BaseModelMbean[null]
                       at org.apache.tomcat.util.modeler.ManagedBean.getGetter(ManagedBean.java:435)
                       at org.apache.tomcat.util.modeler.BaseModelMBean.getAttribute(BaseModelMBean.java:166)
                       at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
                       at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
                       at org.apache.catalina.manager.StatusTransformer.writeConnectorState(StatusTransformer.java:357)

This is somewhat similar to a previous bug but intermittent (https://bz.apache.org/bugzilla/show_bug.cgi?id=62918)
Comment 1 Mark Thomas 2021-06-28 15:12:47 UTC
Once this starts, does it occur for every request or is it intermittent?
Comment 2 Jordan 2021-06-28 15:14:33 UTC
Once it starts it appears to keep happening for every request until server restart.
Comment 3 Mark Thomas 2021-06-28 15:32:04 UTC
Thanks. That is helpful.

I am wondering if the fix for bug 63362 is responsible for this. It made changes in this area and it was in 8.5.60 onwards. No evidence so support this theory yet.
Comment 4 Mark Thomas 2021-06-28 15:38:37 UTC
Yep, that is is. Making a WebSocket request is sufficient to trigger this. Now to figure out a fix.
Comment 5 Mark Thomas 2021-06-28 16:33:35 UTC
Fixed now. Thanks for reporting this.

Fixed in:
- 10.1.x for 10.1.0-M3 onwards
- 10.0.x for 10.0.9 onwards
- 9.0.x for 9.0.51 onwards
- 8.5.x for 8.5.69 onwards