When displaying the thread pools, the StatusManagerServlet ignores executors and uses the 'standard' ThreadPool information for each connector. This causes incorrect information to be displayed when a connector is configured to use an executor. On a related topic, it appears that the connector<->executor link is not exposed via JMX (which it will need to be to fix this).
Created attachment 24272 [details] Patch for 6.0.x Trunk has been fixed and a patch is attached for 6.0.x. The patch ensures that the thread counts returned are correct with or without an executor.
The patch has been proposed for 6.0.x
Comment on attachment 24272 [details] Patch for 6.0.x The patch has been withdrawn as it creates unwanted dependencies
Created attachment 24341 [details] Patch V2 New patch. Can't address issue completely in 6.0.x without fairly invasive changes. Ensure -1 is returned consistently for maxThreads if an executor is in use and return a correct value for the NIO connector where we can.
The new patch has been proposed for 6.0.x
This has been fixed in trunk and will be included in 6.0.21 onwards.