[
https://issues.apache.org/jira/browse/AMQ-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101765#comment-16101765
]
Timothy Bish commented on AMQ-6777:
-----------------------------------
Need a reproducer unit test to validate an issue, not enough information
provided to investigate. You can also attach broker config, and logs from
client and broker around the time of failure. I'd recommend debugging on your
end to see what the client is up to.
> Failover not wokring
> --------------------
>
> Key: AMQ-6777
> URL: https://issues.apache.org/jira/browse/AMQ-6777
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector, Transport
> Affects Versions: 5.14.5
> Environment: Unix
> Reporter: Anil P.
> Priority: Critical
>
> Please refer
> http://activemq.2283324.n4.nabble.com/Active-MQ-Master-Slave-Config-Not-working-td4728550.html#a4728794
> for more details
> When configured as Shared File System Master/Slave, the following two issues
> observed.
> 1) When Master is down, Java clients using
> "failover:(tcp://master:port,tcp:/slave:port)" URL are not falling back /
> connecting to secondary. They are hanging / waiting for connection.
> If I use timeout like
> "failover:(tcp://master:port,tcp:/slave:port)?randomize=false&timeout=<timeout
> in ms>", if I use 1 mnt as timeout, I am getting error saying connection
> timeout when master is stopped/killed. If I use 5 mnts, it is again hanging.
> 2) If the URL is "failover:(tcp://slave:port,tcp:/master:port)", it is
> hanging/waiting infinitely at connection.start();
> Please help.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
