Red Hat Bugzilla – Bug 817778
Default value for "Redistribution Delay" (when creating JMS Queue) is not properly defined in UI
Last modified: 2013-09-03 10:46:05 EDT
Description of problem:
When trying to create new JMS Queue, "Redistribution Delay" default value
should be "-1" but in UI it's just "-" so the user has to change it. Also,
it's not possible to set it to "-1".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In JON UI, select JBoss instance with HornetQ and navigate to JMS Manager;
2. Right click on JMS Manager and from the drop down menu choose "Create Child"
and JMS Queue;
3. Follow the screens in the "Resource Create Wizard" and define values for:
New Resource Name, Name and JNDI Name;
4. Scroll down to check the default value for "Redistribution Delay". This is
set to "-" although the description next to this field says that "-1" is the
default value which means "do not re distribute".
5. Press "Finish" button without changing "Redistribution Delay" value;
The Wizard screen will not close and exclamation sign will be shown next to the
"Redistribution Delay" field.
The "Redistribution Delay" default value is properly set to "-1" and the queue
can be created without changing this field.
Please note that attempt to set this field to "-1" will not work as well.
per BZ triage ... crouch, loleary, foley
Set prio/sev to match JON bug
See comment https://bugzilla.redhat.com/show_bug.cgi?id=817777#c3
Additional info: This problem was noticed when running EAP 5.1.2 + hornetQ enabled.
See comment https://bugzilla.redhat.com/show_bug.cgi?id=817777#c5
Initially I did a test and reported this bug for JBoss ON 3.0.1 (RHQ 4.2) version and EAP 5.1.2 with hornetQ enabled.
However, I've just done the same test on JBoss ON 3.1.2 (RHQ 4.4) with EAP 5.1.2 with hornetQ and this worked fine. The value of "Redistribution Delay" was set to -1 and I got warning and couldn't proceed further when I tried to set this property to some incorrect value (for instance "-").
Bulk closing of issues in old RHQ releases that are in production for a while now.
Please open a new issue when running into an issue.