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 "Kim Haase (JIRA)" <ji...@apache.org> on 2008/04/04 21:29:24 UTC
[jira] Reopened: (DERBY-3540) Document the JMX management and
monitoring functionality
[ https://issues.apache.org/jira/browse/DERBY-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reopened DERBY-3540:
------------------------------
Sorry, meant to leave this open for post-10.4 fixes.
> 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.0.0
> Reporter: John H. Embretsen
> Assignee: Kim Haase
> Fix For: 10.4.1.0
>
> 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.