Bug 1021690

Summary: HornetQ Bridge does not accept all retry values
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Fernando Nasser <fnasser>
Component: HornetQAssignee: Clebert Suconic <csuconic>
Status: CLOSED CURRENTRELEASE QA Contact: Miroslav Novak <mnovak>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.1.1CC: msvehla
Target Milestone: ER9   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-07 08:39:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fernando Nasser 2013-10-21 19:43:43 UTC
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:

Comment 1 Miroslav Novak 2014-07-07 08:39:38 UTC
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.