[
https://issues.apache.org/jira/browse/ARTEMIS-5607?focusedWorklogId=1009125&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1009125
]
ASF GitHub Bot logged work on ARTEMIS-5607:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Mar/26 15:34
Start Date: 11/Mar/26 15:34
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #6278:
URL: https://github.com/apache/artemis/pull/6278#issuecomment-4040079042
Regarding the name `jmx-notification-enabled`, this is consistent with the
naming convention used for other settings (e.g. `jmx-management-enabled`,
`persistence-enabled`, `message-counter-enabled`, etc.). Therefore, I don't
have a problem with the name.
Issue Time Tracking
-------------------
Worklog Id: (was: 1009125)
Time Spent: 0.5h (was: 20m)
> Support disabling JMX notifications
> -----------------------------------
>
> Key: ARTEMIS-5607
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5607
> Project: Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> [JMX
> notifications|https://docs.oracle.com/en/java/javase/17/docs/api/java.management/javax/management/Notification.html]
> are rarely used these days yet the broker still reproduces all management
> notifications as JMX notifications. This is unnecessary overhead in most
> circumstances so we should allow users to disable them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
