[MAGNOLIA-2120] add easy mbean support Created: 23/Apr/08 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
As magnolia becomes to be more and more complex one would like to monitor it (open jcr sessions,...). An easy to use mbean registry would help to forward this. /modules/core/config/mbeans They are registered in the core module's start method Or should it be /server/mbeans ? |
| Comments |
| Comment by Magnolia International [ 23/Apr/08 ] |
|
/modules/xxx/mbeans - each module can then have its own mbeans if needed. |
| Comment by Magnolia International [ 11/Jul/08 ] |
|
Nothing was committed yet, will do for either 3.6.1 or 3.7 |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |