Bug 1021690 - HornetQ Bridge does not accept all retry values
HornetQ Bridge does not accept all retry values
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ (Show other bugs)
6.1.1
Unspecified Unspecified
unspecified Severity unspecified
: ER9
: EAP 6.3.0
Assigned To: Clebert Suconic
Miroslav Novak
Russell Dickenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-21 15:43 EDT by Fernando Nasser
Modified: 2014-07-07 04:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-07-07 04:39:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Fernando Nasser 2013-10-21 15:43:43 EDT
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 04:39:38 EDT
This is already fixed:
[standalone@192.168.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@192.168.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.

Note You need to log in before you can comment on or make changes to this bug.