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 (Commented) (JIRA)" <ji...@apache.org> on 2012/02/02 10:19:53 UTC
[jira] [Commented] (CAMEL-4968) Expose Transacted Redeliveries
statistic in JMX
[ https://issues.apache.org/jira/browse/CAMEL-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198627#comment-13198627 ]
Claus Ibsen commented on CAMEL-4968:
------------------------------------
The stat has been renamed from transacted redeliveries to external redeliveries, as that is a better name. Its a redelivery initiated from an external source, such as a JMS broker.
> Expose Transacted Redeliveries statistic in JMX
> -----------------------------------------------
>
> Key: CAMEL-4968
> URL: https://issues.apache.org/jira/browse/CAMEL-4968
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.9.1, 2.10.0
>
>
> See also CAMEL-4961
> We should expose a TransactedRedeliveries counter as JMX attribute on the Camel routes etc.
> This allow people to know how many redelivered messages they have processed.
> For example when using a JMS broker such as AMQ, and using transaction. Then the JMS broker may send the same message
> back to Camel as a transacted redelivered message. So we should count those in JMX.
> This allows people to know how many unique messages they have processed as its
> unique = total - transacted redeliveries
--
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