Comments on: Enabling JMX monitoring of SEDA Queue Depths in Apache Camel http://www.objectpartners.com/2010/02/15/enabling-jmx-monitoring-of-seda-queue-depths-in-apache-camel/ Object Partners Inc. Tue, 31 Jan 2012 16:52:31 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Claus Ibsen http://www.objectpartners.com/2010/02/15/enabling-jmx-monitoring-of-seda-queue-depths-in-apache-camel/comment-page-1/#comment-445 Claus Ibsen Mon, 15 Feb 2010 17:28:13 +0000 http://www.objectpartners.com/?p=1789#comment-445 The queue depth of the seda endpoint is avail in JMX. Its however avail as an JMX operation because its a BrowsableEndpoint instance. The reason why its not an attribute is that some other BrowseableEndpoints may take to much resources to compute the queue depth (such as JmsEndpoint). See the ManagedBrowsableEndpoint class. I recon we should allow the seda queue to easily be unbounded instead of fixed at 1000. I have created CAMEL-2471 to track that. The queue depth of the seda endpoint is avail in JMX. Its however avail as an JMX operation because its a BrowsableEndpoint instance. The reason why its not an attribute is that some other BrowseableEndpoints may take to much resources to compute the queue depth (such as JmsEndpoint).

See the ManagedBrowsableEndpoint class.

I recon we should allow the seda queue to easily be unbounded instead of fixed at 1000. I have created CAMEL-2471 to track that.

]]>