Bugzilla – Full Text Bug Listing
| Summary: | JMX: Add JMX MBean support to JBoss 5.1.0 EAP as well as JBoss 5/6 CE | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael OBrien <michael.f.obrien> |
| Component: | Eclipselink | Assignee: | Michael OBrien <michael.f.obrien> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | eclipselink.foundation-inbox |
| Version: | unspecified | Flags: | michael.f.obrien:
documentation+
|
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| URL: | http://wiki.eclipse.org/EclipseLink/DesignDocs/248748 | ||
| Whiteboard: | |||
| Bug Depends on: | 305331 | ||
| Bug Blocks: | 316513 | ||
| Attachments: | |||
>JBoss 5.1.0 EAP will be targetted (not 6 at this point)
- MBean registration POC in queue ahead of architecture work
Created attachment 172440 [details]
Container Managed JTA HSQL EclipseLink JPA 1.0 example application EAR for MBean session invocation
>First POC results positive using a non-JNDI JMX spec findMBeanServer() first server returned lookup (fine only for non-JRockit JVMs) >Using the server mBeanServerRuntime = (MBeanServer) MBeanServerFactory.findMBeanServer(null).get(0); >we register via runtimeInstance = mBeanServerRuntime.registerMBean(runtimeServices, anObjectName); >to server MBeanServerImpl (id=400) classLoaderRepository UnifiedLoaderRepository3 (id=409) listeners MBeanServerListenerRegistry (id=417) outer MBeanServerImpl (id=400) classLoaderRepository UnifiedLoaderRepository3 (id=409) listeners MBeanServerListenerRegistry (id=417) outer MBeanServerImpl (id=400) registry BasicMBeanRegistry (id=419) defaultDomain "jboss" (id=426) delegate MBeanServerDelegate (id=427) domainMap ConcurrentReaderHashMap (id=432) fMbInfosToStore null loaderRepository UnifiedLoaderRepository3 (id=409) mbeanInfoService ObjectName (id=436) registrationNotificationSequence SynchronizedLong (id=439) server MBeanServerImpl (id=400) unregistrationNotificationSequence SynchronizedLong (id=444) registry BasicMBeanRegistry (id=419) >giving us 16:56:54,376 INFO [STDOUT] [EL Finest]: 2010-06-22 16:56:54.376--Thread(Thread[http-127.0.0.1-8080-2,5,jboss])--Registered MBean: org.eclipse.persistence.services.jboss.MBeanJBossRuntimeServices[TopLink:Name=Session(vfszip_/C_/opt/jboss-eap-5.0b/jboss-as/server/default/deploy/org.eclipse.persistence.example.jpa.server.jboss.EnterpriseEAR.ear/org.eclipse.persistence.example.jpa.server.jboss.EnterpriseEJB.jar/_example)] runtimeInstance ServerObjectInstance (id=519) agentID "xps435_1277239942304" (id=436) className "org.eclipse.persistence.services.jboss.MBeanJBossRuntimeServices" (id=521) name ObjectName (id=501) _ca_array ObjectName$Property[1] (id=523) _canonicalName "TopLink:Name=Session(vfszip_/C_/opt/jboss-eap-5.0b/jboss-as/server/default/deploy/org.eclipse.persistence.example.jpa.server.jboss.EnterpriseEAR.ear/org.eclipse.persistence.example.jpa.server.jboss.EnterpriseEJB.jar/_example)" (id=524) Created attachment 172623 [details] JBoss 5.0.1 EAP screencap of proof of concept reg/view of Services MBean in JBoss JMX console >POC screen cap using http://wiki.eclipse.org/EclipseLink/DesignDocs/316513#JBoss_Proof_of_Concept_Registration_1 >view after EM creation via EAR application run http://127.0.0.1:8080/enterprise/FrontController?action=demo >via the JBoss JMX console view http://127.0.0.1:8080/jmx-console/ >See full generic patch for JBoss, WebSphere, WebLogic and Glassfish in parent bug# 316513 https://bugs.eclipse.org/bugs/attachment.cgi?id=173897&action=diff >SVN 7792,7789, 7777 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7777 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7789 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7792 >finalization of the refactor is in bug# 316513 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
>EclipseLink currently supports JMX MBeans on WebLogic 10.3 via bug# 248748 >This enhancement starts the investigation extend JMX support to JBoss 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.