db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-3540) Document the JMX management and monitoring functionality
Date Tue, 01 Feb 2011 18:50:29 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase resolved DERBY-3540.
------------------------------

    Resolution: Fixed

No further work on this issue has been suggested for quite a while. Resolving it again.

> 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: DERBY-3540-1.diff, DERBY-3540-2.diff, DERBY-3540-3.diff, cadminconfig86869.html,
cadminconfig86869.html, cdevbabejgjd.html, ctunsetprop824983.html, 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message