A deficiency in the JON UI concerning the allowed values of the keepalive-time unit caused confusion for customers when trying to configure the keepalive-time correctly. The keepalive-time unit field now replaces the previous free-text field with predefined, supported units of measure drop down. Customers can now confidently set the keepalive-time precision easily, without trying to convert a number to the correct unit of measure.
Description of problem:
There is no guidance for the allowed values when specifying the keepalive-time unit. The unit field should be converted to a drop-down that provides the supported values:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attempt to create a thread pool of any type
2. Specify a Keepalive Time.
Keepalive Time Unit field allows any input without guidance on what is expected/required.
Keepalive Time Unit should be a drop-down containing the valid values for this field.
This appears to have been partially captured in bug 825384 but not addressed. It is not clear why we didn't actually address this with some kind of UI feedback to the user. The UI supports drop-down lists and it supports descriptions. It seems that this is something that we should have handled in the first place.
Merged into release/jon3.3.x
Author: Stefan Negrea <firstname.lastname@example.org>
Date: Thu Aug 28 15:08:09 2014 -0500
(cherry picked from commit 7bef780cf4a014e2734e358c46df1f00d1b6a818)
Signed-off-by: Thomas Segismont <email@example.com>
Switched the time unit field from free text to the option set described above by Larry.
Moving to ON_QA as available for test with the following brew build:
Build Number :