[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582707#action_12582707
]
John H. Embretsen commented on DERBY-3435:
------------------------------------------
Thanks for committing, Bernt!
I intend to close this issue within the end of this week unless I hear
objections. Additional improvements or fixes should be tracked by new Jira
issues.
> 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: JMX
> Reporter: John H. Embretsen
> Assignee: John H. Embretsen
> Fix For: 10.4.0.0
>
> Attachments: d3435_javadocUpdates.diff,
> d3435_NetworkServerMBeanTest_v01.diff, d3435_v01.diff, d3435_v01.stat,
> derby-3435-live-data-fix-v0.zip, derby-3435-live-data-fix2-v0.diff,
> derby-3435-live-data-v0.diff, derby-3435-live-data-v0.stat,
> derby-3435-live-data-v1.zip, derby-3435-live-data-v2.zip
>
>
> 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.
