rajdavies wrote:
>
> This is handled by the ActiveMQ failover transport (the default in 5.1
> onwards).
> It replays messages on your behalf that haven't been acknowledged -
>
You refer to the case when the connection was only temporarily lost, and the
client runtime would autonomously do a
djencks wrote:
>
> I looked at the failover docs I could find and I think thabach was
> asking a different question that AFAICT the failover docs don't
> discuss... anyway I've wondered about this question :-) :
>
Right, the concrete scenario I was considering was a simple
(non-transaction
I looked at the failover docs I could find and I think thabach was
asking a different question that AFAICT the failover docs don't
discuss... anyway I've wondered about this question :-) :
Suppose a client sends a message inside a transaction and either the
client or broker crashes before t
This is handled by the ActiveMQ failover transport (the default in 5.1
onwards).
It replays messages on your behalf that haven't been acknowledged -
there is duplicate detection built in to the broker and the clients
too ...
cheers,
Rob
cheers,
Rob
Rob Davies
http://fusesource.com
http:
