it is not a great solution, but you could repeat the tcp://broker1:61616 urla few times. The logic discards the current url on failure and moves on to the next in the list.
There is a backup option, which keeps a hot backup, but if this is created at the same time it may suffer from the same problem. The backup needs a unique url, so if you do repeat the broker1 url, add a query parameter (one that is inconsequential b/c all query parameters must be valid) that uniquely identifies each. like tcp://broker1:61616?jmxPort =1000,tcp://broker1:61616?jmxPort=1001 the jmxPort transport option is only used when trace && dynamicManagement=true which is unusual. On 22 November 2012 19:53, rolin <ro...@wellington.com> wrote: > tcp://broker1:61616 -- http://redhat.com http://blog.garytully.com
