Bug 293367 - Use MXBeans to expose monitoring information about Rules, Jobs and Locks
Summary: Use MXBeans to expose monitoring information about Rules, Jobs and Locks
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-26 16:57 EDT by Min Idzelis CLA
Modified: 2019-09-06 16:12 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Min Idzelis CLA 2009-10-26 16:57:44 EDT 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: 

A lot of the information that is accessible at runtime is not exposed very well. This information is most important when diagnosing things like deadlocks and other threading problems. JobManager should expose information about Locks, Jobs, and Rules via Java Management Beans. An adopter can then write a utility that can collect this information when a hang occurs just like they can do with a java heap dump and stack dump. 

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:12:42 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.