[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566143#action_12566143
]
John H. Embretsen commented on DERBY-1387:
------------------------------------------
@Rick: The rather unhelpful error messages you were seeing are mostly caused by
JConsole not having access to the classes required to unwind the message of the
root cause Exception. Bernt mentioned a work-around for that:
https://issues.apache.org/jira/browse/DERBY-1387?focusedCommentId=12537011#action_12537011
Perhaps it is possible to improve this if the MBeans are implemented a little
differently, I think I saw something about that on the web somewhere (might
require using different MBean types or something, I'll see if I can find a
reference).
The work-around works for all (?) errors except the one you get when shutting
down the server. If the server VM exits when you shutdown the server (true if
you're using NetworkServerControl or derbyrun.jar on the command line), then
the MBeanServer will also exit, so the connection between JConsole and the
server is broken abruptly. Not sure if this is possible to fix for generic JMX
clients such as JConsole.
@All - Security:
So, it seems clear to me from the recent comments that we need to do something
about the security issues. I think we can agree on the following:
A valid JMX user (a user able to connect via JMX to Derby's MBeanServer) should
not be able to access information or perform operations that would otherwise be
restricted by Derby's existing security mechanisms (authentication,
authorization, Security Manager, etc.).
I noticed Dan's suggestion of including a restricted/limited set of
MBeans/attributes/operations in the first version of this feature, which seems
sensible to me. Other ideas are of course welcome.
> 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.
