Bug 908795

Summary: [RFE] The JMX plugin should be able to use JBoss Remoting 3 to connect to EAP6 using JSR-160 remoting
Product: [JBoss] JBoss Operations Network Reporter: Tristan Tarrant <ttarrant>
Component: Plugin -- OtherAssignee: Thomas Segismont <tsegismo>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: kejohnso, myarboro, tsegismo
Target Milestone: ---Keywords: FutureFeature, TestCaseNeeded
Target Release: JON 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-24 15:05:51 UTC Type: Feature Request
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: 919199    

Description Tristan Tarrant 2013-02-07 14:43:41 UTC
In order to allow easy monitoring of user deployments which might expose metrics over JMX, the RHQ JMX plugin needs to be able to use JBoss Remoting 3 to connect to an AS7/EAP6 instance over the remoting port (standalone: 9999, domain: 4447).

This wiki page

https://community.jboss.org/wiki/UsingJconsoleToConnectToJMXOnAS7

describes the additional JARs required to support the 

service:jmx:remoting-jmx://{host_name}:{port}  

URI scheme

Comment 3 Thomas Segismont 2014-07-31 14:40:34 UTC
Fixed in master

commit 73e9bb52dae0c23a616640dd02191bc49ce7ec39
Author: Thomas Segismont <tsegismo>
Date:   Thu Jul 31 16:37:19 2014 +0200

Added new connection metadata (ConnectionTypeDescriptor classes) for:
* AS7 and EAP6.0
* EAP6.1 and above
* Wildfly 8

Added new connection templates for JMX server manual process

Refactored JMX plugin itests

Added itests for AS7 and Wildfly 8 in standalone mode
-> Added the Maven plugins for AS7 and Wildfly 8 in order to start standalone servers
-> add-user script is through an ANT tasks to support both UNIX-like systems and Windows systems

Comment 4 Mike McCune 2016-03-28 23:42:22 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Filip Brychta 2019-06-24 15:05:51 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.