[CAMEL-1933] Overhaul of JMX

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.1, 2.0.0
• Fix Version/s: 2.1.0
• Component/s: jmx
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 25/Aug/09 06:39
• Updated: 03/Jun/10 07:23
• Resolved: 10/Sep/09 12:36

Description

This is a ticket to hold the work of overhaul of the JMX management to be done in Camel 2.1.

Issue Links

• is depended upon by: CAMEL-1484 JMX - Runtime configuration of DSL that supports options
• is depended upon by: CAMEL-1951 camel-jms consumer endpoint should allow properties such as maxConcurrentConsumers and concurrentConsumers to be managed via JMX
• is depended upon by: CAMEL-1976 Restarting JmsConsumer should pickup configuration changes
• is depended upon by: CAMEL-868 Add support to start/stop of routes via JMX

Sub-Tasks

• Overhaul of JMX - Pluggable Management: Closed
• Overhaul of JMX - Add pluggable event notification: Closed
• Overhaul of JMX - Add more details to existing mbeans: Closed
• OVerhaul of JMX - Add Tracer as managed: Closed
• Overhaul of JMX - Fix route not having correct stats: Closed
• Overhaul of JMX - Introduce ManagmentAware to allow other Camel components to provide management capabilities: Closed
• Overhaul of JMX - Add management example: Closed
• Overhaul of JMX - Add route id to processor and consumers: Closed
• Overhaul of JMX - Add documentation to wiki: Closed
• Overhaul of JMX - Easier to disable from Java: Closed
• Overhaul of JMX - Add managed producers: Closed
• Overhaul of JMX - Add granularity level option for performance stats enabled on startup: Closed
• Overhaul of JMX - Add managed error handler: Closed
• Overhaul of JMX - Fire notification event when CamelContext failed during starting or stopping: Closed
• Overhaul of JMX - Only register singleton endpoints to avoid overhead: Closed