Bug 1285357

Summary: [GSS](6.4.z) Port-offset incorrectly displayed in admin console
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ranjith Pulluru <rpulluru>
Component: Web ConsoleAssignee: Ryan Emerson <remerson>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Jelinek <pjelinek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.4CC: bbaranow, bmaxwell, dpospisi, hbraun, hpehl, jawilson, jkudrnac, jochen.riedlinger, jtruhlar, mcada, pjelinek, remerson
Target Milestone: CR1   
Target Release: EAP 6.4.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 11:57:15 UTC 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:
Bug Depends On:    
Bug Blocks: 1274291, 1279552    
Attachments:
Description Flags
Admin console screen-shot none

Description Ranjith Pulluru 2015-11-25 12:59:22 UTC
Created attachment 1098798 [details]
Admin console screen-shot

Description of problem:
=======================
 - Port-offset incorrectly displayed in JBoss EAP 6.4.4 admin console 

Version-Release number of selected component (if applicable):
==============================================================
 - JBoss EAP 6.4.4

Steps to Reproduce:
===================
1) Take a fresh JBoss EAP 6.4.4 version.
2) Configure port-offset in `domain.xml` file under server-groups as below:
-------
 <server-groups>
        <server-group name="main-server-group" profile="full">
            <jvm name="default">
                <heap size="1000m" max-size="1000m"/>
                <permgen max-size="256m"/>
            </jvm>
            <socket-binding-group ref="full-sockets" port-offset="100"/>   <= *Configuration added here
        </server-group>
		:
 </server-groups>
-------
3) No port-offset present in host.xml file and configuration looks as below
-------
    <servers>
        <server name="server-one" group="main-server-group">
        </server>
        :
     </servers>   
-------

4) Then start the JBoss server in domain mode.

5) Open the JBoss EAP 6.4.4 admin console and navigate to 
     Domain tab -> Overview -> Hosts, groups and server instances are displayed.

6) The port-offset for the servers of main-server-group are displayed as 0.

Actual results:
===============
- Port-offset for the servers of main-server-group are displayed as 0 which is wrong.

Expected results:
=================
- Port-offset for the servers of main-server-group should display 100.

Comment 1 JBoss JIRA Server 2015-12-02 15:38:36 UTC
Ryan Emerson <remerson> updated the status of jira HAL-993 to Open

Comment 2 JBoss JIRA Server 2015-12-02 15:38:58 UTC
Ryan Emerson <remerson> updated the status of jira HAL-993 to Coding In Progress

Comment 3 JBoss JIRA Server 2015-12-02 15:40:27 UTC
Ryan Emerson <remerson> updated the status of jira JBEAP-2053 to Closed

Comment 4 JBoss JIRA Server 2015-12-02 15:40:31 UTC
Ryan Emerson <remerson> updated the status of jira JBEAP-2053 to Reopened

Comment 6 JBoss JIRA Server 2015-12-04 12:14:12 UTC
Ryan Emerson <remerson> updated the status of jira JBEAP-2053 to Closed

Comment 7 JBoss JIRA Server 2015-12-04 12:14:17 UTC
Ryan Emerson <remerson> updated the status of jira JBEAP-2053 to Reopened

Comment 8 JBoss JIRA Server 2016-01-25 20:39:01 UTC
Harald Pehl <hpehl> updated the status of jira HAL-993 to Resolved

Comment 9 JBoss JIRA Server 2016-01-25 20:39:43 UTC
Harald Pehl <hpehl> updated the status of jira JBEAP-2053 to Resolved

Comment 12 Michael Cada 2016-03-01 14:25:09 UTC
Verified on EAP 6.4.7.CP.CR2

Comment 13 JBoss JIRA Server 2016-06-14 11:36:57 UTC
Jiri Pallich <jpallich> updated the status of jira JBEAP-2053 to Closed

Comment 14 Petr Penicka 2017-01-17 11:57:15 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.