You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/09/22 20:36:16 UTC

[jira] Commented: (DERBY-3540) Document the JMX management and monitoring functionality

    [ https://issues.apache.org/jira/browse/DERBY-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758348#action_12758348 ] 

Myrna van Lunteren commented on DERBY-3540:
-------------------------------------------

Is there any more to be documented? A number of JMX related bugs were fixed in 10.5 (DERBY-1387, DERBY-3462, DERBY-3657), perhaps they need to be documented?

> Document the JMX management and monitoring functionality
> --------------------------------------------------------
>
>                 Key: DERBY-3540
>                 URL: https://issues.apache.org/jira/browse/DERBY-3540
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JMX
>    Affects Versions: 10.4.1.3
>            Reporter: John H. Embretsen
>            Assignee: Kim Haase
>             Fix For: 10.4.1.3
>
>         Attachments: cadminconfig86869.html, cadminconfig86869.html, cdevbabejgjd.html, ctunsetprop824983.html, DERBY-3540-1.diff, DERBY-3540-2.diff, DERBY-3540-3.diff, tadminconfigsysteminformation.html
>
>
> Brand new management and monitoring capabilities using JMX were starting to be added to Derby in the first calendar quarter of 2008. This issue tracks efforts documenting this functionality.
> A JMX M&M functional specification document (funcSpec.html) is attached to DERBY-1387. More information may be available on the wiki - http://wiki.apache.org/db-derby/DerbyJMX - and in JMX-related Javadocs ("published API") (packages org.apache.derby.mbeans and org.apache.derby.mbeans.drda).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.