[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568933#action_12568933
]
John H. Embretsen commented on DERBY-1387:
------------------------------------------
Thanks for the new revision of the patch. The committed code seems like a
usable starting point for further work. I hope we're able to add some more
useful functionality to it before the 10.4 release - perhaps we could start
with a set of monitoring features that are not as sensitive security-wise as
some of the ones currently in the funcSpec.
Due to the missing security permissions Derby's JMX feature does not currently
work "out of the box" with the Network Server when using default settings
(Security Manager). Although we'll add a set of required permissions to the
default policy later, I am slightly worried that no hints about missing
permissions are given to the user.
When I now run the Network Server with jdk1.4 and JMX enabled, I see the
following in derby.log:
2008-02-14 13:40:44.874 GMT Thread[main,5,main] Class
org.apache.derby.impl.services.jmx.JMXManagementService
java.lang.UnsupportedClassVersionError:
org/apache/derby/impl/services/jmx/JMXManagementService (Unsupported
major.minor version 49.0), module ignored.
The message makes sense to me, but will it make sense to the users?
Also, the fact that the JMXManagementSerrvice now wraps the MBeans in a
StandardMBean has some implications that we (and any Derby MBean developers)
should be aware of. For example, emitting notifications or implementing
MBeanRegistration won't work without some extra effort; see [1]. I think using
StandardMBean (which technically makes our MBeans "dynamic" instead of
"standard") is useful and provides more flexibility, but I just wanted to point
out that it is not necessarily always straight forward.
[1]: http://blogs.sun.com/jmxetc/entry/javax_management_standardmbean_when_and
> 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,
> derby1387_simple_9_1.txt, 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.
