[ https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530654
]
Bernt M. Johnsen commented on DERBY-1387:
-----------------------------------------
On second thought. Making the Derby JMX automatically available in the MBean server will make
it impossible for the user to make some application with an embedded Derby db manageable thorugh
JMX without also making Derby manageable thorugh JMX. I would think that this "all or nothing"
granularity could be a problem for some applications. So we would need an explicit derby.system.jmx
property for enabling the management service anyway. Any comments?
> Add JMX extensions to Derby
> ---------------------------
>
> Key: DERBY-1387
> URL: https://issues.apache.org/jira/browse/DERBY-1387
> Project: Derby
> Issue Type: New Feature
> Components: Services
> Reporter: Sanket Sharma
> Assignee: Bernt M. Johnsen
> Attachments: DERBY-1387-1.diff, DERBY-1387-1.stat, DERBY-1387-2.diff, DERBY-1387-2.stat,
DERBY-1387-3.diff, DERBY-1387-3.stat, DERBY-1387-4.diff, DERBY-1387-4.stat, derbyjmx.patch,
jmx.diff, jmx.stat, jmxFuncspec.html, Requirements for JMX Updated.html, Requirements for
JMX.html, Requirements for JMX.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.