Bug 1039933 - Server Port
Summary: Server Port
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Miroslav Sochurek
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 11:11 UTC by Nick Cross
Modified: 2019-02-22 22:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Enhancement

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1123416 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1123416

Description Nick Cross 2013-12-10 11:11:01 UTC 
The Installer starts the server to run the CLI on the default port. Would it be possible to start it with a 
-Djboss.socket.binding.port-offset=<random-offset>
so that there is less change of it conflicting with any currently running servers started on the default port?
Comment 2 Thomas Hauser 2014-02-19 18:42:56 UTC 
There is currently a check to see if the default port is being used before installation is allowed to continue. In my opinion, that should be a sufficient warning. Perhaps we could refine this BZ?
Comment 3 Thomas Hauser 2014-07-29 15:25:36 UTC 
The bug I've added to the 'see also' section is asking for something very similar to this.
Note You need to log in before you can comment on or make changes to this bug.