[jboss-jira] [JBoss JIRA] (JGRP-1894) JmxConfigurator logging improvements
[
https://issues.jboss.org/browse/JGRP-1894?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1894:
--------------------------------
Rather than adding a parameter to {{unregister()}}, the code tries to unregister all
protocols anyway, but checks first if a protocol is registered with the MBeanServer before
doing so.
JmxConfigurator logging improvements
------------------------------------
Key: JGRP-1894
URL: https://issues.jboss.org/browse/JGRP-1894
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.2.13
Reporter: Dennis Reed
Assignee: Bela Ban
Priority: Minor
Fix For: 3.6
JmxConfigurator is overly verbose about logging some things, and doesn't log enough
in other cases.
- unregisterChannel does not have an equivalent for registerChannel(...,
register_protocols=false)
It will log a WARN message for each protocol if the channel was registered with
register_protocols=false
- several places log an exception at ERROR level then throw it.
If the exception is being thrown, it generally should not be logged above DEBUG
- a few spots catch and log an exception message but do not throw it
These should also log the full stack trace at DEBUG
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)