activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petter Nordlander <Petter.Nordlan...@enfo.se>
Subject Re: delay failover transfer
Date Mon, 05 May 2014 05:37:46 GMT
There is actually rather good documentation about such features on
http://activemq.apache.org/failover-transport-reference.html.

I would check out the ²priorityBackup² feature, that will try to keep the
connection to a primary broker, if possible. It might or might not suit
your needs.

failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBac
kup=true

However, your connection should not drop on a simple sub second network
lag. Something else is dropping your connection.


I would also reconsider configuring the broker network in a way that you
don¹t lose messages. A switch might cost some slight delay (use the backup
feature to avoid that delay), but shouldn¹t affect the client more than
that.


BR Petter



Den 2014-05-05 04:40 skrev Charels_Li <iamleejt@gmail.com>:

>The network of my firm was built a couple of years ago, whose bandwidth is
>limited. We are afraid there could be some lag/jam in data transmission.
>Say, a client losses contact with the broker due to an occasional network
>lag, but the connection could come to life after 2/3 seconds. In this
>case,
>we dont like the client switch forward/ backward for it could create some
>delay and message loss.
>
>Shall i use failover transport? Or there's some sophisticated configs i
>could try?
>
>
>
>--
>View this message in context:
>http://activemq.2283324.n4.nabble.com/delay-failover-transfer-tp4680504p46
>80841.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message