[
https://issues.jboss.org/browse/WFCORE-4710?page=com.atlassian.jira.plugi...
]
Andrew Dinn commented on WFCORE-4710:
-------------------------------------
Thanks for looking at this Brian. I'm sure you know far better than I do what the
solution is.
It is actually quite lucky the error method was passed the escaped name as otherwise the
message would have been even more confusing.
I'm not at all surprised this has not turned up before. Changes to the buffer pool are
rare and changes which install names with e.g. spaces that need escaping even more so. Let
me know if you have problems recreating this.
Wrong BufferPoolMXBean name used in lookup
------------------------------------------
Key: WFCORE-4710
URL:
https://issues.jboss.org/browse/WFCORE-4710
Project: WildFly Core
Issue Type: Enhancement
Components: JMX
Affects Versions: 10.0.0.Final
Reporter: Andrew Dinn
Assignee: Brian Stansberry
Priority: Major
Class BufferPoolMXBeanResource transforms the name of retrieved MXBeans to handle
embedded spaces and other special characters by calling method escapeMBeanName. Later on
class BufferPoolMXBeanResourceAttributeHandler uses the name to identify the corresponding
bean. Unfortunately, when BufferPoolMXBeanResourceAttributeHandler checks that the bean is
registered it does not reverse the transformation by calling unescapeMBeanName.
This causes a lookup failure when the new buffer pool non-volatiel memory MXBean is
encountered on JDK14. Although Wildlfy appears to continue running the error message
appears to cause failures in some of the Wildfly tests, notably those that check error
stream output.
See the referenced forum thread for full details.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)