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

Bug 846650

Summary: JBossAS7 resource name does not reflect port-offset
Product: [JBoss] JBoss Operations Network Reporter: Martin Gencur <mgencur>
Component: UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: high    
Version: JON 3.1.1CC: myarboro
Target Milestone: ---   
Target Release: JON 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-05 21:15:01 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:
Attachments:
Description Flags
JON GUI with two resources with the same name none

Description Martin Gencur 2012-08-08 10:48:02 UTC 
Created attachment 602993 [details]
JON GUI with two resources with the same name

Description of problem:

When I set up 2 different instances of JBossAS 7 (I actually used JDG) and one of them has port-offset, the resource name in UI is still the same and says: JDG (127.0.0.1:9990). Actually, it should display JDG (127.0.0.1:10090) for one of the instances cos I set port-offset=100.

When I change this in the connection settings, the resource name does NOT change. However, this was already reported in BZ 846578.

Attaching screenshot...
Comment 1 Martin Gencur 2012-08-08 10:49:40 UTC 
I found this in JON 3.1.1 ER1
Comment 2 mark yarborough 2012-09-25 20:17:36 UTC 
Will investigate... Is this a problem in the JDG plugin?
Comment 3 Charles Crouch 2012-09-25 20:18:39 UTC 
We need to determine if this occurs with vanilla AS7, if it does we should fix the as7 plugin. Otherwise it should be pushed to the JDG team.
Comment 4 Martin Gencur 2012-09-26 06:26:43 UTC 
Tomas Sykora later tested JDG plugin with JON 3.1.1 CR2 and he did not see this issue anymore. My guess is that this is not in JDG plugin because the plugin did not change in last 3 months.