Bug 917036
| Summary: | Custom port binding collisions are not detected | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Petr Kremensky <pkremens> | ||||
| Component: | Installer | Assignee: | Jyoti Tripathi <jtripath> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | jtripath, tkirby | ||||
| 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: | 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: |
|
||||||
http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=ca508c72f55fc322f78329f153d6e0c7d5e50111 http://git.app.eng.bos.redhat.com/?p=izpack.git;a=commit;h=126dcf89c70ff06ae0f96612967f66452c9ab0a9 Gui is working fine. There is still one think I don't like when using -console installation. If I make some collision (ajp and http port in this case), I will stuck on last item (txn-status-manager in this case) where I can only cancel the installation, which is however in any case better, then installing server with port collisions. I think that if some collisions were detected, user should be able to re-enter port numbers.
...
Socket Bindings
Configure the socket bindings for JBoss Enterprise Application Platform 6.
Select Port Configuration:
0 [x] Use the default port bindings for standalone and domain modes.
1 [ ] Configure custom port bindings.
Input Selection:
1
[x] Configure ports for standalone mode
Input 1 to select, 0 to deselect:
1
[x] Configure ports for domain mode
Input 1 to select, 0 to deselect:
0
press 1 to continue, 2 to quit, 3 to redisplay.
1
Socket Binding (standalone)
------------------------------------------
ajp Port Number [8009]
8080
http Port Number [8080]
https Port Number [8443]
management-native Port Number [${jboss.management.native.port:9999}]
management-http Port Number [${jboss.management.http.port:9990}]
management-https Port Number [${jboss.management.https.port:9443}]
osgi-http Port Number [8090]
remoting Port Number [4447]
txn-recovery-environment Port Number [4712]
txn-status-manager Port Number [4713]
Validation error.: check Port Number
txn-status-manager Port Number [4713]
Validation error.: check Port Number
txn-status-manager Port Number [4713]
fixed the console behavior, now all ports for that configuration need to be re-entered after a validation error Verified, port number collisions are now detected and user is able to re-enter them. There is still an issue with port range validation for domain, but there is bz for this (BZ923747) so closing this one. |
Created attachment 704163 [details] possible custom binding Collisions in custom socket binding should be detected same as we detect correct port range. I am able to enter same port number for every value (see attachment). This will naturally lead to: Address already in use /127.0.0.1:8080 during server startup.