https://bz.apache.org/bugzilla/show_bug.cgi?id=62871
--- Comment #1 from Mark Thomas <ma...@apache.org> --- 8.0.x is no longer supported. If you made a similar change in 8.5.x I'm fairly sure you'd just hit the next unserializable attribute. Changing visibility is not really the right solution as it just hides the information and there is a lot of valuable data in that attribute. Making the attribute Serializable is one option but that requires that either the class is present on the JMX client's class path or RMI is enabled to load the class remotely. In this instance, making SocketProperties Serializable will just move the problem as a bunch of its attributes will then fail. Creating a separate MBean for SocketProperties has the same issue. Similar issues exist throughout the Tomcat MBeans. Looking at your config, am I correct in thinking you are just interested in the ThreadPool MBeans? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org