Bug 1046059

Summary: Web console says -1 is an "Invalid numeric value" while setting reconnect attempts on connection factory
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: varsha <vkamble>
Component: Web ConsoleAssignee: Harald Pehl <hpehl>
Status: CLOSED DUPLICATE QA Contact: Jakub Cechacek <jcechace>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, hbraun, jkudrnac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-09 12:38:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
"Invalid numeric value" message shown in web console while setting reconnect-attempts = -1 none

Description varsha 2013-12-23 12:23:46 UTC
Created attachment 840791 [details]
"Invalid numeric value" message shown in web console while setting reconnect-attempts = -1

Description of problem:
Web console says -1 is an "Invalid numeric value" while setting ReconnectAttempts on connection factory. Also it shows ReconnectAttempts value 0 if it is set to -1 in configuration file.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Set reconnect-attempts value through CLI as below :

[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=reconnect-attempts,value=-1)
{"outcome" => "success"}
[standalone@localhost:9999 /]

2. check it through Web console, it shows value set to 0.

3. Try to edit value to -1, it gives message as "Invalid numeric value".


Actual results:


Expected results:


Additional info:

Comment 1 Heiko Braun 2014-07-09 12:38:44 UTC

*** This bug has been marked as a duplicate of bug 1018800 ***