[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570772#action_12570772
]
John H. Embretsen commented on DERBY-3435:
------------------------------------------
Thanks for the commit. Seems like you forgot to actually move the MBean
interface to java/drda (?) - now I see the org.apache.derby.mbeans.drda package
in java/engine as well as in java/drda.
The suggested javadoc comments seem valid to me.
The host property is a bit tricky as always (probably because it should be
called derby.drda.connectionInterface or some such instead). The suggested
"0.0.0.0" description change is fine, although the first sentence of the
javadoc should be something like
"Gets the name of the network interface on which the network server is
listening"
instead of
"Gets the host name for the network server"
;-)
> Add an MBean for monitoring and managing the Network Server
> -----------------------------------------------------------
>
> Key: DERBY-3435
> URL: https://issues.apache.org/jira/browse/DERBY-3435
> Project: Derby
> Issue Type: Sub-task
> Components: Network Server, Services
> Reporter: John H. Embretsen
> Assignee: John H. Embretsen
> Attachments: d3435_v01.diff, d3435_v01.stat
>
>
> Most functionality of and information about a running instance of the Network
> Server is currently only available from the host running the Network Server,
> using the NetworkServerControl API.
> With a JMX Management and Monitoring service in place utilizing JMX
> (DERBY-1387), it is possible to expose some of the Network Server
> functionality and information through an MBean that is specific to the
> Network Server, to both local and remote users (JMX clients), subject to
> security restrictions. Access to Derby libraries on the client side is not
> even a requirement, potentially making a server administrator's job a lot
> easier.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
