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 Wed, 20 Feb 2008 16:57:43 GMT

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

John H. Embretsen commented on DERBY-3435:

Thanks for looking at the patch!

Package placement: No reason, I just didn't think of placing it in java/drda, so feel free
to move it.

The Exception handling issue is known from DERBY-1387 - I did not provide a solution as part
of this patch.

Yes, the ping command requires a SocketPermission (as stated above). Even with the permission
I'm not sure it will always work, since the NetworkServerControlImpl instance is not designed
to ping itself. For example, if "-h" is specified, it pings the host instead
of localhost (which works, but there may be other values of -h that won't, I guess).

I agree with the javadoc suggestion and that the implementation class should be package private.

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