[DERBY-1387] Add JMX extensions to Derby

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: JMX
• Assignee: John Embretsen
• Reporter: Sanket Sharma
• Created: 08/Jun/06 18:06
• Updated: 01/Jul/09 00:34
• Resolved: 04/Apr/08 15:49

Description

This is a draft requirement specification for adding monitoring and management extensions to Apache Derby using JMX. The requirements document has been uploaded on JIRA as well as the Derby Wiki page at http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX

Developers and Users are requested to please look at the document (feature list in particular) and add their own rating to features by adding a coloumn to the table.

Comments are welcome.

Issue Links

• blocks: DERBY-2109 System privileges
• incorporates: DERBY-3424 Add an MBean that an application can register to change the state of Derby's JMX management

Sub-Tasks

• Tests for JMX Management and Monitoring: Closed
• Remove system property derby.system.jmx: Closed
• Add an MBean for monitoring and managing the Network Server: Closed
• Require new permissions in o.a.d.security.SystemPermission to allow control to Derby's JMX management and to ensure information is not leaked through JMX: Closed
• Investigate ability to run multiple Derby systems in same JVM with different sets of MBeans.: Closed
• Add JMX testing with a security manager and investigate testing with JMX authentication.: Closed