Community
Participate
Working Groups
>EclipseLink currently supports JMX MBeans on WebLogic 10.3 via bug# 248748 >This enhancement starts the investigation extend JMX support to JBoss and WebSphere and optionally Glassfish We are splitting the enhancement request by application server, the actual analysis, design and implementation will have aspects that are common to all 3 or 4 of these sub-requests. >The work here involves making WLS support use the generic framework being developed for the other application servers
Created attachment 173055 [details] JRockit MC JConsole cap showing services MBean after non-JNDI (JMX spec factory) generic registration (for all platforms)
Comment on attachment 173055 [details] JRockit MC JConsole cap showing services MBean after non-JNDI (JMX spec factory) generic registration (for all platforms) >The refactor of registration to ServerPlatformBase is working for all 3 servers WebLogic, JBoss and WebSphere without using server specific JNDI lookups) http://wiki.eclipse.org/EclipseLink/DesignDocs/316513#Option_2:_Direct_factory_reference_via_JMX_API
>This work is in progress via enhancement bug# 316513 - the POC where we move all registration up to the abstract superclass is working
*** Bug 253018 has been marked as a duplicate of this bug. ***
Created attachment 173063 [details] Preliminary snapshot patch of generic refactor of WebLogic platform JMX registration (multiple MBeanServer handlers pending)
*** Bug 318032 has been marked as a duplicate of this bug. ***
>See bug# 316513 in rev# 7777, 7844 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7844 >remaining work is the getApplicationName(), getModuleName() implementations for non WebLogic EE servers
.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink