Bug 900466 (JBPAPP6-1238) - Installer: option in the ports screen that would provide a choice of offset ports
Summary: Installer: option in the ports screen that would provide a choice of offset p...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBPAPP6-1238
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 6.1.0
Assignee: Alex Szczuczko
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On: JBPAPP6-1242 JBPAPP6-1243 JBPAPP6-1244
Blocks: JBPAPP6-1248
TreeView+ depends on / blocked
 
Reported: 2012-05-18 15:26 UTC by Dustin Kut Moy Cheung
Modified: 2014-06-28 12:33 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-08 18:49:59 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP6-1238 0 Major Closed Installer: option in the ports screen that would provide a choice of offset ports 2013-09-10 18:42:09 UTC

Description Dustin Kut Moy Cheung 2012-05-18 15:26:36 UTC
project_key: JBPAPP6

[11:17:26] < fnasser-mtg> I need you guys to think about an option in the ports screen that would provide a choice:
[11:17:37] < fnasser-mtg> 1) default numbers
[11:17:46] < fnasser-mtg> 2) default numbers with +1 offset
[11:17:55] < fnasser-mtg> 3) Default numbers with +100 offset
[11:18:03] < fnasser-mtg> 4) Spefified offset
[11:18:44] < fnasser-mtg> (add entry box with max 65535 positive integer
[11:20:54] < fnasser-mtg> This will allow one to easily install an alternate server that runs in parallel with the one that may already be running in the system

Comment 1 Brian Stansberry 2012-05-21 19:58:48 UTC
There is a configuration for the port-offset; see the xsd for the socket-binding-group element. IMHO it makes more sense to expose that in the installer than to have the installer itself calculate a bunch of offsets and then change all the individual port numbers.

Comment 2 Dustin Kut Moy Cheung 2012-05-22 12:34:04 UTC
Thanks Brian for the suggestion! That actually simplifies a lot our task! :)

Comment 3 Dustin Kut Moy Cheung 2012-05-22 18:11:25 UTC
Brian: I don't see a port-offset attribute on the socket-binding-group element for domain.xml.

So, does the offset only apply to standalone or can we add a port-offset attribute in domain.xml?




Comment 4 Brian Stansberry 2012-05-22 19:28:28 UTC
Dustin,

See socket-binding-group-refType in the xsd -- that's what's used in a managed domain.

    <xs:complexType name="socket-binding-group-refType">
        <xs:attribute name="ref" type="xs:string">
            <xs:annotation>
                <xs:documentation>
                    The socket group to use for the server group or server.
                </xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
            <xs:annotation>
                <xs:documentation>
                    Increment to apply to the base port values defined in the
                    referenced socket group to derive the values to use on this
                    server.
                </xs:documentation>
            </xs:annotation>
        </xs:attribute>
    </xs:complexType>

In a managed domain, the domain.xml socket-binding-group settings are meant to be applied across the domain. While a port-offset is more server specific. So in the managed domain configurations, the place where the port-offset is configured is on the server-specific configuration elements, either <server-group> in domain.xml or <server> in host.xml. I think the latter would be the more common way to use it.

Comment 5 Alex Szczuczko 2012-05-22 20:56:17 UTC
Brian:

Could you look at the screenshot in [this subtask|https://issues.jboss.org/browse/JBPAPP-9108]? What do you think of the design?

Thanks.

Comment 6 Dustin Kut Moy Cheung 2012-05-24 18:27:59 UTC
Link: Added: This issue is a dependency of JBPAPP-8085


Comment 7 Dustin Kut Moy Cheung 2012-05-29 14:47:59 UTC
Waiting for translations before this JIRA is marked as resolved. Right now all relevant commits have been done and they are in the portOffset branches

Comment 8 Dustin Kut Moy Cheung 2012-07-23 14:34:24 UTC
Link: Added: This issue is a dependency of JBPAPP-9555


Comment 9 Dustin Kut Moy Cheung 2012-07-23 14:34:26 UTC
This issue could not make it to EAP6.0.0 because of lack of translations. Hopefully it will make it in EAP 6.1

Comment 10 Dustin Kut Moy Cheung 2012-07-26 13:20:22 UTC
Link: Removed: This issue is a dependency of JBPAPP-8085 


Comment 11 Thomas Hauser 2012-11-08 18:49:59 UTC
This will appear in EAP 6.1

Comment 12 Anne-Louise Tangring 2012-11-13 20:46:42 UTC
Docs QE Status: Removed: NEW 



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