Hello, Although marked as RESOLVED before(#62918 and #63641), I'm having same issue on 8.5.51. Could you check this issue? The Error trace is; javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.SocketProperties@399200be at org.apache.tomcat.util.modeler.ManagedBean.getGetter(ManagedBean.java:435) at org.apache.tomcat.util.modeler.BaseModelMBean.getAttribute(BaseModelMBean.java:167) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647) at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) at newManager.StatusTransformer.writeConnectorState(StatusTransformer.java:250) at newManager.StatusManagerServlet.doGet(StatusManagerServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:543) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:609) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1623) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)
I found out there was error in my configuration. I guess there is no issue on tomcat, so i'll close it now. sorry
I also met this error, but I have no idea. Could you share your Configuration and point what's the matter before. I will be so appreciated. (In reply to Jaeyoon "Jay" Lee from comment #1) > I found out there was error in my configuration. > I guess there is no issue on tomcat, > so i'll close it now. > sorry
(In reply to Vision from comment #2) > I also met this error, but I have no idea. Could you share your > Configuration and point what's the matter before. I will be so appreciated. > (In reply to Jaeyoon "Jay" Lee from comment #1) > > I found out there was error in my configuration. > > I guess there is no issue on tomcat, > > so i'll close it now. > > sorry I was using custom version of tomcat manager, which was developed by another team of our company. The problem was, the manager didn't know about new subtype(subtype=SocketProperties). Since our team didn't use the metrics that the manager provided, i simply removed the manager from my configuration. i.e. I removed following line from my server.xml <Context path="/managerAgent" debug="0" privileged="true" docBase="managerAgent.war" /> I hope this could help you!
(In reply to Jaeyoon "Jay" Lee from comment #3) > (In reply to Vision from comment #2) > > I also met this error, but I have no idea. Could you share your > > Configuration and point what's the matter before. I will be so appreciated. > > (In reply to Jaeyoon "Jay" Lee from comment #1) > > > I found out there was error in my configuration. > > > I guess there is no issue on tomcat, > > > so i'll close it now. > > > sorry > > I was using custom version of tomcat manager, which was developed by another > team of our company. > The problem was, the manager didn't know about new > subtype(subtype=SocketProperties). > Since our team didn't use the metrics that the manager provided, i simply > removed the manager from my configuration. > > i.e. > I removed following line from my server.xml > <Context path="/managerAgent" debug="0" privileged="true" > docBase="managerAgent.war" /> > > I hope this could help you! Anyway, thanks for your reply. If I found something, keep posted.
(In reply to Jaeyoon "Jay" Lee from comment #3) > (In reply to Vision from comment #2) > > I also met this error, but I have no idea. Could you share your > > Configuration and point what's the matter before. I will be so appreciated. > > (In reply to Jaeyoon "Jay" Lee from comment #1) > > > I found out there was error in my configuration. > > > I guess there is no issue on tomcat, > > > so i'll close it now. > > > sorry > > I was using custom version of tomcat manager, which was developed by another > team of our company. > The problem was, the manager didn't know about new > subtype(subtype=SocketProperties). > Since our team didn't use the metrics that the manager provided, i simply > removed the manager from my configuration. > > i.e. > I removed following line from my server.xml > <Context path="/managerAgent" debug="0" privileged="true" > docBase="managerAgent.war" /> > > I hope this could help you! BTW, I met this error when tomcat port is 8080, but it works well on port 8081. That makes me so confused.