[
https://issues.apache.org/jira/browse/QPID-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027812#comment-15027812
]
Alex Rudyy commented on QPID-6913:
----------------------------------
Keith,
After removal of JMX ports and leaving JMX plugin record in initial
configuration I see the following warning in the Broker log:
{noformat}
WARN [Broker-Config] (o.a.q.s.j.JMXManagementPluginImpl) - JmxManagement
plugin is configured but no suitable JMX ports are available.
{noformat}
IMHO, we can change the log level to info for the above or remove jmx plugin
record from initial configuration. However, with the latter users would be
required to edit configuration manually in order to restore JMX functionality.
Presence of the plugin makes a false impression that JMX interfaces would be
present without a remote access via ports but in fact no Qpid JMX MBean are
created with such configuration.
> Remove JMX from default configuration
> -------------------------------------
>
> Key: QPID-6913
> URL: https://issues.apache.org/jira/browse/QPID-6913
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> JMX support in the Broker has been superseded by REST for several major
> versions (~0.24) and has been marked as deprecated in the documentation.
> It is now time to remove JMX from the default configuration.
> It is planned that the next major version of the Broker will not offer JMX in
> its current form.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
