From derby-dev-return-85935-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Fri Mar 04 19:06:00 2011 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 34629 invoked from network); 4 Mar 2011 19:06:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Mar 2011 19:06:00 -0000 Received: (qmail 667 invoked by uid 500); 4 Mar 2011 19:06:00 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 631 invoked by uid 500); 4 Mar 2011 19:06:00 -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 624 invoked by uid 99); 4 Mar 2011 19:06:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Mar 2011 19:06:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Mar 2011 19:05:57 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id DCC114F236 for ; Fri, 4 Mar 2011 19:05:36 +0000 (UTC) Date: Fri, 4 Mar 2011 19:05:36 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: <2078425132.14901.1299265536900.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1197335317.1144.1298009952376.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Commented: (DERBY-5051) Update the docs to include the additional information available in derby.log. This information will be useful from product supportability stand point MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002785#comment-13002785 ] Rick Hillegas commented on DERBY-5051: -------------------------------------- Hi Kim, I am not an expert on Mamta's changes but I have taken a quick look at your patch and it seems good to me. In particular, the extra blurb about the deregister property is welcome. Thanks. > Update the docs to include the additional information available in derby.log. This information will be useful from product supportability stand point > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-5051 > URL: https://issues.apache.org/jira/browse/DERBY-5051 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.8.0.0 > Reporter: Mamta A. Satoor > Assignee: Kim Haase > Attachments: DERBY-5051.diff, DERBY-5051.stat, DERBY-5051.zip > > > With DERBY-4853, we log additional information in derby.log to make it easier for the support group to work with customer problems. > Following 2 additional properties will now always be put in derby.log (every time a database is booted) > user.dir > derby.system.home > user.dir is the system property which gives the user working directory. > If the user has not specified derby,system.home, then Derby will look for optional derby.properties file in user.dir . If user has provided derby.system.home, then the optional derby.properties will be looked in derby.system.home rather than user.dir > If user has not provided derby.system.home, then a sample of the 2 properties on derby.log looks as follows on my machine > user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 > derby.system.home=null > If user has set derby.system.home to c:./temp, then a sample of the 2 properties on derby.log looks as follows on my machine > user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 > derby.system.home=c:/temp > In addition to the above 2 properties, there can be following 3 optional properties in the log (following the 2 properties mentioned above) > derby.stream.error.file > derby.stream.error.method > derby.stream.error.field > The above 3 properties provide a way to alter where error messages get logged rather than tranditional derby.log file. In the absence of the above 3 optional properties, the location of derby.log follows the same logic as derby.properties. But if the user has set any or all of the 3 optional properties, then derby.log will not be in same location as derby.properties. In the Derby code, derby.stream.error.file takes precedence over the other 2 properties and derby.stream.error.method take precedence over the last property. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira