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

Unexpected classloader when registering MBeans that are part of a deployment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 22.0.0.Beta2, 22.0.0.Final
    • None
    • JMX
    • None

    Description

      I initially opened it as a bug for further consideration since I'm not sure what should be the expected behaviour here but when a managed bean is registered as part of a deployment using a service descriptor, the lifecycle methods that registers and unregisters the beans are invoked under the "org.jboss.as.sar" module classloader.

      This seems to be a bit counterintuitive since I would expect them to be executed under the application module classloader so it gets access to all the services or dependencies added to the current deployment.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. WFLY-17833 Angus Activation services are not visible to SAR MBeans

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - A task that needs to be done. WFLY-18370 Remove org.eclipse.angus.activation dependency from sar module, and add test that the App CL is being used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-25937 [GSS](7.4.z) Thread's context classloader for ServiceMBeanSupport startService is not application module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-25942 [GSS](8.0.z) Thread's context classloader for ServiceMBeanSupport startService is not application module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: