Bug 1022400 - Wrong error message while setting port offset in console installer
Summary: Wrong error message while setting port offset in console installer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: CR1
: EAP 6.2.0
Assignee: Francisco Canas
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-23 08:31 UTC by Petr Kremensky
Modified: 2014-09-03 04:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:17:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Kremensky 2013-10-23 08:31:07 UTC
Description of problem:
There is wrong error message when user tries to configure an offset for all default port bindings. It says "Offset value is too large. Maximum offset possible is 0."

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER6

How reproducible:
 Always

Steps to Reproduce:
 1. Run console instalation: java -jar jboss-eap-6.2.0.ER6-installer.jar -console
 2. Follow:
Select Port Configuration:
0  [x] Use the default port bindings for standalone and domain modes.
1  [ ] Configure custom port bindings.
2  [ ] Configure an offset for all default port bindings.
Input Selection: 
2

Select Offset Type
0  [x] +1 offset
1  [ ] +100 offset
2  [ ] Specify offset
Input Selection: 
2
Offset value: []
1111

Actual results:
 Validation error.: Offset value is too large. Maximum offset possible is 0.

Expected results:
 Validation error.: Offset value is too large. Maximum offset possible is $MAXIMUM_OFFSET.

Comment 1 Francisco Canas 2013-10-23 20:05:52 UTC
I've added the a maximum offset based on the largest default port number.

Comment 2 Petr Kremensky 2013-11-15 09:12:21 UTC
Verified on EAP 6.2.0.CR1 installer.


Note You need to log in before you can comment on or make changes to this bug.