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

Bug 1091009

Summary: JON 3.2.0 does not show metrics for Web session and EJB statistics in Domain mode
Product: [JBoss] JBoss Operations Network Reporter: Lami Akagwu <lakagwu>
Component: UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: loleary
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-06 20:49: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:

Description Lami Akagwu 2014-04-24 15:13:48 UTC 
Description of problem:

When connected to an EAP in domain mode 6.1.1 / 6.2.0, JON 3.2.0.GA does not show the deployment information
When connected to a standalone EAP (same version), deployment information is shown ( including Web session and EJB statistics)

Version-Release number of selected component (if applicable):
JON 3.2.0, EAP 6.1.1, EAP 6.2.0

How reproducible:
Always

Steps to Reproduce:
1.Install JON 3.2.0 on a server
2.Start up EAP 6.2.0/EAP 6.1.1 in domain mode
3.Deploy and EAR and a WAR to via the domain controller
4.The metrics are not available for the WAR or EAR
5.Repeat step 3 for a standalaone mode, the metrics for the WAR and EAR are available

Actual results:
EJB metrics and deployment information is not available in domain mode.

Expected results:
Metrics should be available regardless of whether EAP is running in domain or standalone mode

Additional info:
Comment 1 Larry O'Leary 2014-05-06 20:49:01 UTC 
This seems to be a duplicate of bug 912478 and bug 1034218.

Closing as duplicate. If there is something different with this version of the bug, please comment.

*** This bug has been marked as a duplicate of bug 1034218 ***