Is it possible to use MultiCast for failover, but in the event that all those
brokers become unavailable, you would use a static ip address?
failover://(discovery:multicast://default,tcp://test.you.com:61616)
--
View this message in context:
http://www.nabble.com/Failover--use-multicast%2C-then
I have seen this same behaviour an am interested in any info on this!
david.la wrote:
>
> Hi,
>
> I'm using activemq with camel and when i turn the debug logs, I'm seeing
> activity every second or so. It's adding and removing consumer.
>
> I'd like to know what is that for may be i'm miscon
I have set the producer time to live value to expire messages after 10 sec.
However, if the sys clock on the producer is different than the brokers,
chances are high that this 10 sec window will never be realized and ALL
messages will be considered expired. I saw the timeStampingBrokerPlugin is
th
More info on my issue:
Setup:
Running a producer locally, with TTL set to 3000ms (on my laptop)
Connecting to remote broker via mulitcast
I set my laptop clock back 5 min and try to hit the broker with the correct
time. I get this...
DEBUG RegionBroker - Message expired Activ
The clients currently find our brokers by using the multicast://default
discovery, however, I am tasked to log what servers are used to perform the
messaging, once a connection is made. When I retrieve the brokerURL on the
session, it is always multicast://default. There does not seem to be any
m
