[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570739#action_12570739
]
Daniel John Debrunner commented on DERBY-3435:
----------------------------------------------
I'll commit the patch in a few minutes with a minor change:
changed the implementation of the bean to be package private.
Minor comments.
The ping command didn't work for me, maybe a permission issue.
I also think the javadoc for the ping operation should clearly indicate it's a
ping from the same machine as the network server.
Exception handling for ping and the set methods (when added) may need changing.
If the exception chain includes a class that is not present on the client. I
hit this yesterday with a EmbedSQLException from a test MBean.
> 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.
