Description of problem: When entering large value to numeric field, it overflows to -1 (and then the form is showing 0). Version-Release number of selected component (if applicable): EAP 6.2.0.ER5 How reproducible: Go for example to Profile -> Messaging -> Clustering -> Discovery. Go to edit mode and add 1111111111111111111 to Initial Wait Timeout field. Upon save, the value shown in console is 0, if I enter the edit mode again, there's no value at all, CLI and Tools -> Management Model show -1.
Make sure it's reallu a UI issue. To me it's sounds like a server side problem
Heiko, When I go in CLI client to /subsystem=messaging/hornetq-server=default/discovery-group=dg-group1 and call :write-attribute(name=initial-wait-timeout,value=1111111111111111111) result is { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } and ls indeed shows attribute initial-wait-timeout set to that value. If I go to web console after that, I see value -1 for that discovery group. When I enter edit mode the form shows 1111111111111111111 (correct value).
Heiko Braun <ike.braun> updated the status of jira HAL-439 to Coding In Progress
Heiko Braun <ike.braun> updated the status of jira HAL-439 to Resolved
Should this still remain in POST state?
For EAP 6.4.0.DR12 in webconsole numeric fields it seems that there is validation that avoids enter numeric values same or larger than 2^31 regardless if it is possible to enter such value via CLI.
Try enter long value larger than 2^31 to initial-wait-timeout of some discovery group /profile=full/subsystem=messaging/hornetq-server=default/discovery-group=dgroup:write-attribute(name=initial-wait-timeout,value=123456789012345678) { "outcome" => "success", "result" => undefined, "server-groups" => {"main_server_group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "success", "response-headers" => { "operation-requires-restart" => true, "process-state" => "restart-required" } }}, "server-two" => {"response" => { "outcome" => "success", "response-headers" => { "operation-requires-restart" => true, "process-state" => "restart-required" } }} }}}} } The operation vith the same value is not allowed in webconsole. You get 'Invalid numeric value' validation warning. Moreover if you have this value so large (e.g. updated via CLI as above) webconsole show you 0 as value of Initial Wait Timeout. The problem is probably caused by integer data type for this attribute in admin console instead of long.
Heiko Braun <ike.braun> updated the status of jira HAL-439 to Reopened
Harald Pehl <hpehl> updated the status of jira HAL-439 to Resolved
Fixed in Ballroom 2.3.1
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions