Description of problem: Currently we can only specify failure-retry-interval and max-retries To have a proper behavior we'd also need to be able to specify: retry-interval-multiplier max-retry-interval Version-Release number of selected component (if applicable): HornetQ Server version 2.3.9.Snapshot (2.3.8, 123) How reproducible: always Steps to Reproduce: 1. Try and specify the above elements as in a core bridge 2. 3. Actual results: XML error Expected results: retry in increasing intervals until maximum as per parameters Additional info:
This is already fixed: [standalone.40.1:9999 cluster-connection=my-cluster] ./:write-attribute(name=retry-interval-multiplier,value=1.5) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone.40.1:9999 cluster-connection=my-cluster] ./:write-attribute(name=max-retry-interval, value=20000) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } I'll close this bz.