Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 38904 invoked from network); 8 Mar 2008 23:59:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Mar 2008 23:59:07 -0000 Received: (qmail 92546 invoked by uid 500); 8 Mar 2008 23:59:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 92518 invoked by uid 500); 8 Mar 2008 23:59:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 92509 invoked by uid 99); 8 Mar 2008 23:59:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Mar 2008 15:59:03 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Mar 2008 23:58:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3343F234C090 for ; Sat, 8 Mar 2008 15:57:46 -0800 (PST) Message-ID: <1733020280.1205020666208.JavaMail.jira@brutus> Date: Sat, 8 Mar 2008 15:57:46 -0800 (PST) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3435) Add an MBean for monitoring and managing the Network Server In-Reply-To: <277570663.1203436963983.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner updated DERBY-3435: ----------------------------------------- Derby Info: (was: [Patch Available]) NetworkServerMBean test patch applied: Revision: 635115 > 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_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.