We use Camel's JMX feature to report the overall stats/status of all the routes in our application (e.g. ManagedRouteMBean).
However the routes often make heavy use of Camel's choice option where we have multiple when/simple options and then if no matches are found we use an otherwise/stop to make that a no-op for that route. The problem is the JMS reporting is wrong from the user's perspective as Camel includes all of the otherwise/stop entries which should not be included from the user's perspective. How can I remove from the ManagedRouteMBean metrics the files/messages that were not actually processed by the route and were a no-op via the otherwise/stop? Is there a way in the otherwise/stop I can remove that file from JMX metrics? -Dave
