Thanks Tim
2013/11/20 Timothy Creswick :
>however the client isn't able to resolve the name that it receives.
That makes sense for for me , but client's machine has got these
entries in its hosts file
It's weird. Maybe I'm not doing the right tests
So far, I'm going to disable that feature
Rega
> javax.jms.JMSException: java.net.UnknownHostException
See my earlier posts on this subject, but the problem is that your broker is
sending connection details for the other brokers to your client, however the
client isn't able to resolve the name that it receives.
For example, if you have two
I could find out that this error is caused by updateClusterClients="true"
So, I need to se it to false
Thanks
2013/11/20 Jose María Zaragoza :
> Hello:
>
> I'm using AMQ 5.8.0
>
> I've defined the next transport failover
>
> "failover:(tcp://broker1:61616?connectionTimeout=3000,tcp://broke
Hello:
I'm using AMQ 5.8.0
I've defined the next transport failover
"failover:(tcp://broker1:61616?connectionTimeout=3000,tcp://broker2:61616?connectionTimeout=3000)?timeout=5000&startupMaxReconnectAttempts=1&maxReconnectAttempts=1&randomize=false&priorityBackup=false"
I start a Consumer, conn
