Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 74560 invoked from network); 10 Aug 2007 12:30:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Aug 2007 12:30:06 -0000 Received: (qmail 42225 invoked by uid 500); 10 Aug 2007 12:30:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 42014 invoked by uid 500); 10 Aug 2007 12:30: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 42005 invoked by uid 99); 10 Aug 2007 12:30:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2007 05:30:03 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2007 12:30:03 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 97AFB71413F for ; Fri, 10 Aug 2007 05:29:42 -0700 (PDT) Message-ID: <31919800.1186748982602.JavaMail.jira@brutus> Date: Fri, 10 Aug 2007 05:29:42 -0700 (PDT) From: "Bernt M. Johnsen (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#action_12519008 ] Bernt M. Johnsen commented on DERBY-1387: ----------------------------------------- Great work, Ole Gunnar. I will take it from here. The following issues needs to be resolved: 1) make compilation of the jmx parts optional and dependent on wether jmxri.jar is present in tools/java (jmxri.jar is necessary for compiling and for running jmx in jdk 1.4) 2) make JMX work in embedded mode (seems to be a trivial issue) 3) make the start command more simple for the default case 4) testing 5) Consider reducing the number of properties exposed through JMX. There is a conflict here between ease of use for the average user and the usability for the advanced user. > 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: Bernt M. Johnsen > 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, derbyjmx.patch, jmx.diff, jmx.stat, jmxFuncspec.html, 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.