You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 18:45:37 UTC
[jira] [Created] (CAMEL-5091) Do not register ProducerCache in JMX
as they dont bring much value
Do not register ProducerCache in JMX as they dont bring much value
------------------------------------------------------------------
Key: CAMEL-5091
URL: https://issues.apache.org/jira/browse/CAMEL-5091
Project: Camel
Issue Type: Improvement
Components: camel-core, jmx
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.10.0
We should consider not registering ProducerCache mbean in JMX as they are an mostly internal in use by the EIPs.
And for end users they do not bring much value, and just add more mbeans for them to stare at in jconsole.
Also each <to> in the Camel routes has its own producer cache, and thus you can have many producer cache mbeans in JMX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5091) Do not register ProducerCache in JMX
as they dont bring much value
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5091.
--------------------------------
Resolution: Fixed
> Do not register ProducerCache in JMX as they dont bring much value
> ------------------------------------------------------------------
>
> Key: CAMEL-5091
> URL: https://issues.apache.org/jira/browse/CAMEL-5091
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.10.0
>
>
> We should consider not registering ProducerCache mbean in JMX as they are an mostly internal in use by the EIPs.
> And for end users they do not bring much value, and just add more mbeans for them to stare at in jconsole.
> Also each <to> in the Camel routes has its own producer cache, and thus you can have many producer cache mbeans in JMX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira