You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/08/20 23:02:27 UTC
[jira] [Closed] (AMQ-3394) Better Fault Tolerance
[ https://issues.apache.org/jira/browse/AMQ-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3394.
-----------------------------
Resolution: Not A Problem
Configuration issue.
> Better Fault Tolerance
> ----------------------
>
> Key: AMQ-3394
> URL: https://issues.apache.org/jira/browse/AMQ-3394
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.5.0
> Reporter: Darren Govoni
>
> Other queue technologies provide a manner of fault tolerance missing from AMQ message semantics.
> That is, messages can be acknowledged at any time by a client. Failing to do so within the messages TTL, should result in the message re-appearing on the queue so another client can re-try it.
> Reliable messaging with AMQ currently pertains to only message receipt, but in practical systems distributing work via a queue this is unsufficient semantics to ensure tolerance of faults "during" work processing. In that case, clients will only acknowledge a message in the event of successful processing of that message (left to the client to decide). If the client were to suffer a fatality during processing, the work associated with the message is left undone in the current AMQ because it cannot be re-processed. In these extreme (but not uncommon) fault conditions, it is not possible for the client to "re-queue" the message.
> Combining TTL, re-queue behavior (in the Broker) and INDIVIDUAL_ACKNOWLEDGE (on the client) of messages should achieve the desired increase in fault-tolerance described here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira