activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Client reaction to server failure
Date Thu, 09 Jul 2015 13:46:07 GMT
I believe there is no way to guarantee once-and-only-once delivery in the
face of failures; there will always be race conditions that allow the two
sides of the interaction to believe different things about whether the
transaction succeeded or failed, and you have to choose whether you'd
rather have at-least-once delivery or at-most-once delivery.  Pick your
poison, and design your system to be tolerant of whichever one you pick.

On Wed, Jul 1, 2015 at 1:00 PM, jlindwall <jlindwall@yahoo.com> wrote:

> I should add that our messages are sent as persistent messages.
>
> It has been my belief that this means the messages are saved to persistent
> storage before the publish() call is acknowledged; therefore if the master
> broker goes down at that instant, the slave will awaken and pick up
> delivering that message to all consumers.
>
> Reading this blog entry by Christian Posta makes me question my belief
> though:
>
>
> http://blog.christianposta.com/guaranteed-messaging-for-topics-the-jms-spec-and-activemq/
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Client-reaction-to-server-failure-tp4698426p4698447.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message