Community
Participate
Working Groups
The eclipselink.register.run.mbean property check within the WebLogic_10_Platform class uses: shouldRegisterRuntimeBean = System.getProperty(JMX_REGISTER_RUN_MBEAN_PROPERTY) != null; Meaning that even setting a -Declipselink.register.run.mbean=false will end up having the mbean deployed. Users should be able to pass in the eclipselink.register.run.mbean property rather than just being set through system properties, and the value should be respected - allowing it to be turned on/off instead of just on.
>The fact that "any" text will enable the property needs to be addressed in the common abstract platform class for WebLogic, JBoss and WebSphere for bug# 316513
>something like changing protected boolean shouldRegisterRuntimeBean = System.getProperty(JMX_REGISTER_RUN_MBEAN_PROPERTY) != null; >to protected boolean shouldRegisterDevelopmentBean = false; ..in the constructor or a static block String shouldRegisterRuntimeBeanProperty = System.getProperty(JMX_REGISTER_RUN_MBEAN_PROPERTY); if(null != shouldRegisterRuntimeBeanProperty && shouldRegisterRuntimeBeanProperty.toLowerCase().indexOf("true") > -1) { shouldRegisterRuntimeBean = true; }
>this was by design - see line // Any value such as true will turn on the MBean
Created attachment 174157 [details] SVN rev# 7792 Enable true(new default) and false for MBean registration options
>Fixed in SVN rev# http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7792
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink