db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3435) Add an MBean for monitoring and managing the Network Server
Date Tue, 26 Feb 2008 14:50:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572504#action_12572504

John H. Embretsen commented on DERBY-3435:

Thanks for helping out adding some useful statistics to the MBean, Bernt! Feel free to reassign
this issue if you don't plan on creating a separate one.

I hope to fix the Javadoc issues (mentioned in previous comments) before the 10.4 release
(unless someone else volunteers), but I'll be on vacation for about one week starting tomorrow,
so I won't be able to do it just yet. I'll check the status of this issue when I get back.

> 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:
>         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
> 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.

View raw message