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

Unexpected classloader when registering MBeans that are part of a deployment


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

      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.

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