Bug 840965 - as7 plugin should not include thread ids as part of platform-mbean > threading resource configuration
as7 plugin should not include thread ids as part of platform-mbean > threadin...
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
Unspecified Unspecified
high Severity high (vote)
: ---
: JON 3.1.1
Assigned To: Armine Hovsepyan
Mike Foley
Depends On: 837903
Blocks: as7-plugin
  Show dependency treegraph
Reported: 2012-07-17 13:45 EDT by Heiko W. Rupp
Modified: 2016-03-30 15:34 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 837903
Last Closed: 2013-09-03 11:13:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
threadIds_NotAvailable (185.62 KB, image/png)
2012-08-13 08:48 EDT, Armine Hovsepyan
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2214151 None None None 2016-03-30 15:34 EDT

  None (edit)
Description Heiko W. Rupp 2012-07-17 13:45:53 EDT
+++ This bug was initially created as a clone of Bug #837903 +++

Right now the as7 plugin defines threading resources (key=core-service=platform-mbean,type=threading). Part of the configuration for this resource is a property called "All Thread Ids" which is described as "All live thread IDs. If a security manager is installed and the caller does not have ManagementPermission('monitor'), the result will be undefined." When editing the configuration it is not possible alter this list in any way (see threading-config-current.png). Also it does not make sense to try to alter this list, since its really just diagnostic information about the JVM.

My suggestion is to remove the "All Thread Ids" property from the resource configuration, simply because it is not a configuration property for this property. An alternative implementation could move this facility to an operation where by people are interested in getting the thread ids of the running jvm could do so as they are needed.

One side-effect of the "All Thread Ids" property is that the configuration for the threading resource keeps getting rediscovered every 30mins (see threading-config-history.png) This is because the value of the "All Thread Ids" property is constantly changing as the JVM executes so our config checker thread on the agent keeps finding an updated config each time it runs. 

The fix for this issue should make sure that the "All Thread Ids" property is removed for all AS7 instances added to inventory going forward, but also for all AS7 resources which were in the inventory prior to this fix (i.e. update those as part of upgrading)

--- Additional comment from ccrouch@redhat.com on 2012-07-05 15:01:04 EDT ---

Created attachment 596478 [details]
Threading resource configuration

--- Additional comment from ccrouch@redhat.com on 2012-07-05 15:02:15 EDT ---

Created attachment 596479 [details]
Threading resource configuration history

--- Additional comment from hrupp@redhat.com on 2012-07-09 06:13:22 EDT ---

Change in plugin has been pushed to master as e704b68

I do not think there is any need to change the update code, as I was having an AS in inventory that showed the thread ids in config, and after plugin update they were just gone.

--- Additional comment from ccrouch@redhat.com on 2012-07-09 13:28:12 EDT ---

As part of the QE for this issue we need to make sure that the thread ids are no longer getting collected for existing resources
Comment 1 Stefan Negrea 2012-07-31 05:49:12 EDT
release/jon3.1.x branch commit:

Comment 2 John Sanda 2012-08-02 14:52:12 EDT
JON 3.1.1 ER1 build is available. Moving to ON_QA.

Comment 3 Armine Hovsepyan 2012-08-13 08:48:49 EDT
Created attachment 603988 [details]

Comment 4 Heiko W. Rupp 2013-09-03 11:13:49 EDT
Bulk closing of old issues in VERIFIED state.

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