Bug 1012521 - Rename Max Retry to Max Retry Interval in messaging clustering settings
Summary: Rename Max Retry to Max Retry Interval in messaging clustering settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER9
: EAP 6.3.0
Assignee: Harald Pehl
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-26 15:10 UTC by Martin Svehla
Modified: 2015-02-01 23:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 14:36:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-315 0 Minor Resolved Rename Max Retry to Max Retry Interval in messaging clustering settings 2014-07-08 13:15:56 UTC

Description Martin Svehla 2013-09-26 15:10:57 UTC 
Description of problem:
In Profile -> Messaging -> Clustering -> Connections. Property Max Retry should be renamed to Max Retry Interval. I understand that the full name is rather long, but calling it just Max Retry is misleading (it should be obvious that it's time interval, not number of attempts).

Version-Release number of selected component (if applicable):
EAP 6.2.0.ER3
Comment 1 JBoss JIRA Server 2013-12-13 10:12:00 UTC 
Harald Pehl <hpehl> updated the status of jira HAL-315 to Resolved
Comment 2 Martin Velas 2014-07-08 13:05:34 UTC 
Verified for EAP 6.3.0.ER9.
Note You need to log in before you can comment on or make changes to this bug.