Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 923747

Summary: Port validation in installer is working only for standalone part
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: InstallerAssignee: Jyoti Tripathi <jtripath>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.1.0CC: jtripath, thauser, tkirby
Target Milestone: ER5   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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
Possible domain custom binding none

Description Petr Kremensky 2013-03-20 11:47:12 UTC
Created attachment 713193 [details]
Possible domain custom binding

Port binding collisions check and port number validation is executed only for standalone socket binding settings. 
See attachment. User should be warned as it is in standalone settings.

Comment 1 Petr Kremensky 2013-04-03 12:23:54 UTC
*Just for info*
Current situation (ER4)

port collisions are now detected also for domain
port range validation is still not working (this is same no matter if using gui or console)

Comment 2 Petr Kremensky 2013-04-18 08:41:12 UTC
This is still broken. 

GUI - standalone
enter 9999 (collision with mgmt native port) or 9990 (collision with mgmt http port) to ajp port number is not detected.

console - standalone
OK

GUI, console - domain
OK

GUI, console - ha-domain, full-domain, full-ha-domain
collisions are not detected at all

Comment 3 Petr Kremensky 2013-04-24 07:11:09 UTC
Verified on EAP 6.1.0 ER5