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

Bug 1039933

Summary:	Server Port
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Nick Cross <ncross>
Component:	Installer	Assignee:	Miroslav Sochurek <msochure>
Status:	CLOSED UPSTREAM	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	soa-p-jira
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:	2025-02-10 03:34:35 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.

Comment 7 Red Hat Bugzilla 2025-02-10 03:34:35 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.