Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/DesignDocs/332312"

m (EclipseLink Application Analytics, Monitoring, Performance and Diagnostics)
m (EclipseLink Application Analytics, Monitoring, Performance and Diagnostics)
Line 1: Line 1:
=EclipseLink Application Analytics, Monitoring, Performance and Diagnostics=
+
=EclipseLink Application Management, Analytics, Diagnostics and Performance=
 
*[http://bugs.eclipse.org/332312 Enhancement Request 332312]
 
*[http://bugs.eclipse.org/332312 Enhancement Request 332312]
 
==Problem==
 
==Problem==
 +
*This enhancement details work that will be done to enhance our basic JMX management API and add additional support for diagnostics and analytics reporting.
 +
*There are two issues to this enhancement that separately deal with management and diagnostics reporting. 
 +
===Management API===
 +
*Our existing runtime JMX management API that is exposed through the services MBean in any of the SUN JConsole, JRockit JRMC, Oracle JRF Enterprise Manager or JBoss web based console is sufficient but needs to be enhanced.
 +
===Diagnostics API===
 +
*Our existing runtime performance monitoring API could be enhanced with more JVM reporting - ideally that would not itself add overhead.  This type of monitoring is currently done with JRockit - however it does not specifically target the JPA runtime API.
 
==Scope==
 
==Scope==
 
*The scope of this issue is limited to the primary EE application servers that we currently support via JMX.  These are WebLogic, WebSphere, GlassFish and JBoss.  We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container.
 
*The scope of this issue is limited to the primary EE application servers that we currently support via JMX.  These are WebLogic, WebSphere, GlassFish and JBoss.  We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container.

Revision as of 11:18, 11 February 2011

EclipseLink Application Management, Analytics, Diagnostics and Performance

Problem

  • This enhancement details work that will be done to enhance our basic JMX management API and add additional support for diagnostics and analytics reporting.
  • There are two issues to this enhancement that separately deal with management and diagnostics reporting.

Management API

  • Our existing runtime JMX management API that is exposed through the services MBean in any of the SUN JConsole, JRockit JRMC, Oracle JRF Enterprise Manager or JBoss web based console is sufficient but needs to be enhanced.

Diagnostics API

  • Our existing runtime performance monitoring API could be enhanced with more JVM reporting - ideally that would not itself add overhead. This type of monitoring is currently done with JRockit - however it does not specifically target the JPA runtime API.

Scope

  • The scope of this issue is limited to the primary EE application servers that we currently support via JMX. These are WebLogic, WebSphere, GlassFish and JBoss. We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container.

Requirements

  • Official high level requirements = 1) Make our management framework better
  • R1: Address critical open issues general to all application servers
  • R2: Expand platforms that we support JMX management on
    • R2.1: Expand support for JMX management of JPA based applications to SE clients
    • R2.2: Expand support for JMX management of JPA based applications to JEE6 EJB3.1 container managed deployments

Constraints

Assumptions

Analysis

Design

Implementation

Testing

References

Competitive Intelligence

Back to the top