From derby-dev-return-55334-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Feb 19 20:21:18 2008 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 26028 invoked from network); 19 Feb 2008 20:21:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Feb 2008 20:21:18 -0000 Received: (qmail 66188 invoked by uid 500); 19 Feb 2008 20:21:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 66161 invoked by uid 500); 19 Feb 2008 20:21:12 -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 66152 invoked by uid 99); 19 Feb 2008 20:21:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2008 12:21:12 -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; Tue, 19 Feb 2008 20:20:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7D5BF234C04D for ; Tue, 19 Feb 2008 12:20:43 -0800 (PST) Message-ID: <1940118388.1203452443512.JavaMail.jira@brutus> Date: Tue, 19 Feb 2008 12:20:43 -0800 (PST) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1387) Add JMX extensions to Derby In-Reply-To: <4163741.1149764849905.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-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570415#action_12570415 ] John H. Embretsen commented on DERBY-1387: ------------------------------------------ By "Users" I basically meant Network Server VM administrators. As far as I know, the permissions allow Derby's code to instantiate the MBeanServer if needed and register, unregister and be the source of MBeans. I think there is strictly no concept of users, especially no distinction between local and remote users, in this context...(?), though the source (codebase) of the actions may make a difference. Is there a possibility that such permissions are not needed? > Add JMX extensions to Derby > --------------------------- > > Key: DERBY-1387 > URL: https://issues.apache.org/jira/browse/DERBY-1387 > Project: Derby > Issue Type: New Feature > Components: Services > Reporter: Sanket Sharma > Assignee: John H. Embretsen > Attachments: DERBY-1387-1.diff, DERBY-1387-1.stat, DERBY-1387-2.diff, DERBY-1387-2.stat, DERBY-1387-3.diff, DERBY-1387-3.stat, DERBY-1387-4.diff, DERBY-1387-4.stat, DERBY-1387-5.diff, DERBY-1387-5.stat, DERBY-1387-6.zip, DERBY-1387-7.zip, DERBY-1387-8.zip, DERBY-1387-9.diff, DERBY-1387-9.stat, derby1387_simple_9_1.txt, derbyjmx.patch, jmx.diff, jmx.stat, jmxFuncspec.html, jmxFuncspec.html, jmxFuncspec.html, jmxPolicyFileChanges_v1.diff, Requirements for JMX Updated.html, Requirements for JMX.html, Requirements for JMX.zip > > > This is a draft requirement specification for adding monitoring and management extensions to Apache Derby using JMX. The requirements document has been uploaded on JIRA as well as the Derby Wiki page at http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX > Developers and Users are requested to please look at the document (feature list in particular) and add their own rating to features by adding a coloumn to the table. > Comments are welcome. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.