https://issues.apache.org/jira/browse/TOMEE-1296
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 20:15 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Ok think I get i, that's a tomee bug. I'll try to fix it tonight > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-08-18 20:02 GMT+02:00 Bjorn Danielsson > <[email protected]>: >> Andy, no I didn't modify any startup scripts. I tried adding >> -Dcom.sun.management.jmxremote=true just now and nothing changed. >> >> When I crank up eclipselink.logging.level the logs show that the >> eclipselink "MBeanDevelopmentServices" is registered, but the next >> mbean is null. That's the "MBeanRuntimeServices" mbean if you look >> in the eclipselink source code. But here my understanding stops >> unfortunately. >> >> -- >> Bjorn Danielsson >> Cuspy Code AB >> >> >> Andy Gumbrecht <[email protected]> wrote: >>> Are you setting the properties -Declipselink.register.run.mbean=true, >>> or -Declipselink.register.dev.mbean=true >>> If so then then you will require -Dcom.sun.management.jmxremote=true - >>> This used to be on/true by default, but was removed from the release. >>> >>> Andy. >>> >>> On 18/08/2014 16:40, Bjorn Danielsson wrote: >>>> Can't get a stack trace, just the warning. But after peeking in >>>> the Eclipselink source code it seems clear the thing that is null >>>> is this variable, which is supposed to hold a platform-specific >>>> Eclipselink MBean: >>>> >>>> JMXServerPlatformBase.runtimeServicesMBean >>>> >>>> And adding this in tomee/conf/system.properties makes the warning >>>> go away: >>>> >>>> eclipselink.register.run.mbean=false >>>>
