-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
7.6.3
-
7.06
-
3
-
Severity 3 - Minor
-
1
-
Problem
If JMX is enabled during startup, it won't actually expose any of the Jira attributes.
Steps to Reproduce
- Enable JMX Monitoring in Jira
- Restart
- Connect JConsole
- Check the MBeans for com.atlassian.jira
- Notice:
Expected Behaviour
The Jira attributes mentioned here would be shown:
Actual Behaviour
We see com.atlassian.jira, but only the datasource within it. None of the Jira attributes are visible.
Workaround
- Disable JMX in Jira and then Re-enable it
- Disconnect JConsole and reconnect
- is duplicated by
-
JRASERVER-67534 JMX doesn't work correctly after restarting instance
-
- Closed
-
- is related to
-
JRASERVER-67466 Expose Jira and performance metrics through JMX (part1)
- Closed
[JRASERVER-66802] JMX does not share Jira Attributes on Initial Startup
Fixed in Enterprise Release/s | New: [Download 7.6|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html] |
Minimum Version | New: 7.06 |
Workflow | Original: JAC Bug Workflow v2 [ 2835056 ] | New: JAC Bug Workflow v3 [ 2924991 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2631884 ] | New: JAC Bug Workflow v2 [ 2835056 ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is related to |
Fix Version/s | Original: 7.6.5 [ 78515 ] |
Fix Version/s | New: 7.6.5 [ 78515 ] |
Fix Version/s | New: 7.6.6 [ 79690 ] | |
Fix Version/s | Original: 7.6.7 [ 79717 ] |