[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565864#action_12565864
]
Daniel John Debrunner commented on DERBY-1387:
----------------------------------------------
I can see the argument for disallowing Derby's jmx beans (by setting
derby.system.jmx=false) and probably it should be an opt-in system (ie. mbeans
off by default).
Having derby.system.jmx being static though is a huge pain, seems that most
useful would be the ability to enable mbeans against a running system.
Also having the ability at the database level to control its DatabaseMBean
would seem useful (i.e. a database can indicate if it will register a
DatabaseMBean or not).
I don't think any of these are essential for this work, but it may be something
to think about, especially around the api of enabling system or database
mbeans. A single boolean property may be too inflexible and cause confusion if
a finer-grained scheme is added later.
One thought is to have a simple mbean that controls if other mbeans are
enabled. This meta-mbean would require system authentication to enable other
mbeans (e.g. a property or operation to start the system mbean). Probably
requires the mbean security model to be worked out first.
> 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: John H. Embretsen
> 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, DERBY-1387-5.diff, DERBY-1387-5.stat, DERBY-1387-6.zip,
> DERBY-1387-7.zip, DERBY-1387-8.zip, DERBY-1387-9.diff, DERBY-1387-9.stat,
> derbyjmx.patch, jmx.diff, jmx.stat, jmxFuncspec.html, jmxFuncspec.html,
> 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.
