On Wed, Feb 24, 2010 at 2:31 PM, Josh Carlson wrote:
> Hi Gary,
>
> Thanks for the explanation. The order is:
>
> consumer retrieves message
>
> connection is lost and consumer re-establishes connection to new master
> broker
>
> consumer acks the message retrieved from the former broker
Hi Gary,
Thanks for the explanation. The order is:
consumer retrieves message
connection is lost and consumer re-establishes connection to new
master broker
consumer acks the message retrieved from the former broker
consumer retrieves the same message it just ack'ed.
I gues
On failover, redispatch of unacked messages will occur and this is
unordered. There is no guarantee that the same consumer will get the same
messages after failover of a connection.
On the java client there is a message audit that will suppress duplicates
that may occur, I think the same is true fo
When using a shared file system master/server activemq configuration and
client acknoledgements we run into a problem when
our clients fail over to a new server. The problem is that the new
server does not appear to have any knowledge of pending
messages that the old server had dispatched to clie
