tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62871] JMX: ThreadPool.socketProperties is not Serializable
Date Thu, 01 Nov 2018 23:10:06 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62871

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Mark Thomas <markt@apache.org> ---
The root cause is that the Endpoint (ThreadPool) MBeans are generated via
introspection so it is non-trivial to filter out unwanted attributes and/or
operations. If an mbeans-descriptors.xml was used, the filtering would be
trivial as the entries could just be removed.

There are a lot of attributes so manually generating the content for an
mbeans-descriptors.xml file would be time consuming. I've created a tool to
extract this data using the introspection code as a starting point:
https://github.com/markt-asf/tomcat-bugs/blob/master/src/java/org/apache/tomcat/MBeanDump.java

That allowed me to easily create an mbeans-descriptors.xml file for the
Endpoints which I then edited to remove the broken attributes and operations. I
also added a SWocketProperties Mbean although that looks like it would benefit
from some refactoring.

Fixed in:
- trunk for 9.0.13 onwards
- 8.5.x for 8.5.35 onwards

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message