Hi Martin javax.management.MBeanServer service is exposed by Karaf Management bundle.
I just checked in 4.2.9, and I can see the service available: objectClass = [javax.management.MBeanServer] service.bundleid = 30 service.id = 83 service.scope = singleton Does it mean that the service is not available anymore when you add the dynatrace agent ? Maybe the dynatrace agent creates its own MBeanServer, overriding the Karaf one ? Can you check with the service:list command if you see the MBeanServer service available (or bundle:server with karaf.management bundle id) ? Regards JB > Le 2 sept. 2020 à 15:31, Martin Lichtin <[email protected]> a écrit : > > Having an issue with a Karaf deployment that is supervised by Dynatrace. > > After upgrading from Karaf 14.1.7 to 4.2.9, the JMX bean server reference (in > blueprint) > > <reference id="mbeanServer" interface="javax.management.MBeanServer" /> > > is no longer available. Seeing "unresolved dependencies > [(objectClass=javax.management.MBeanServer)]" at startup. > > Would anyone have any experience with Dynatrace Agent having such an effect? > > Once we remove loading the agent at startup, this issue disappears. > > - Martin >
