Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4710

Wrong BufferPoolMXBean name used in lookup

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 11.0.0.Beta1, 11.0.0.Final
    • 10.0.0.Final
    • JMX
    • None

      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.

              bstansbe@redhat.com Brian Stansberry
              rhn-engineering-adinn Andrew Dinn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: