db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1069837 - in /db/derby/docs/trunk/src: devguide/cdevdvlp20458.dita ref/crefproper22250.dita ref/refderby.ditamap ref/rrefproperlogboottrace.dita
Date Fri, 11 Feb 2011 15:31:15 GMT
Author: chaase3
Date: Fri Feb 11 15:31:15 2011
New Revision: 1069837

URL: http://svn.apache.org/viewvc?rev=1069837&view=rev
Log:
DERBY-4727: Document derby.stream.error.logBootTrace=true diagnostic property

Modified 1 Dev Guide topic; added new Ref Manual property topic, modified map and properties
intro topic.

Patches: DERBY-4727.diff

Added:
    db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita   (with props)
Modified:
    db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
    db/derby/docs/trunk/src/ref/crefproper22250.dita
    db/derby/docs/trunk/src/ref/refderby.ditamap

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita?rev=1069837&r1=1069836&r2=1069837&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita Fri Feb 11 15:31:15 2011
@@ -34,7 +34,11 @@ for details.
 ERROR XSDB6: Another instance of Derby may have already booted the
 database /home/myself/DERBYTUTOR/firstdb.
 </codeblock>
-<p>In addition, a stack trace appears in the <i>derby.log</i> file.</p>
+<p>In addition, a stack trace appears in the <i>derby.log</i> file. For
help
+diagnosing a double boot problem, use the
+<i>derby.stream.error.logBootTrace</i> property to obtain information about
+both successful and unsuccessful boot attempts. The property is described in
+the <ph conref="../conrefs.dita#pub/citref"></ph>.</p>
 <p>If you need to access a single database from more than one
 Java Virtual Machine (JVM), you will need to put a server solution in place. You
 can allow applications from multiple JVMs that need to access that database to

Modified: db/derby/docs/trunk/src/ref/crefproper22250.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/crefproper22250.dita?rev=1069837&r1=1069836&r2=1069837&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/crefproper22250.dita (original)
+++ db/derby/docs/trunk/src/ref/crefproper22250.dita Fri Feb 11 15:31:15 2011
@@ -272,6 +272,11 @@ colwidth="38*"/>
 <entry colname="3">&nbsp;</entry>
 </row>
 <row>
+<entry colname="1"><i><xref href="rrefproperlogboottrace.dita#rrefproperlogboottrace">derby.stream.error.logBootTrace</xref></i></entry>
+<entry colname="2">S</entry>
+<entry colname="3">&nbsp;</entry>
+</row>
+<row>
 <entry colname="1"><i><xref href="rrefproper26985.dita#rrefproper26985">derby.stream.error.logSeverityLevel</xref></i></entry>
 <entry colname="2">S</entry>
 <entry colname="3">&nbsp;</entry>

Modified: db/derby/docs/trunk/src/ref/refderby.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/refderby.ditamap?rev=1069837&r1=1069836&r2=1069837&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/refderby.ditamap (original)
+++ db/derby/docs/trunk/src/ref/refderby.ditamap Fri Feb 11 15:31:15 2011
@@ -767,6 +767,8 @@ URL syntax"></topicref>
 </topicref>
 <topicref href="rrefproper18151.dita" navtitle="derby.stream.error.file">
 </topicref>
+<topicref href="rrefproperlogboottrace.dita" navtitle="derby.stream.error.logBootTrace">
+</topicref>
 <topicref href="rrefproper26985.dita" navtitle="derby.stream.error.logSeverityLevel">
 </topicref>
 <topicref href="rrefproper35028.dita" navtitle="derby.stream.error.method">

Added: db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita?rev=1069837&view=auto
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita (added)
+++ db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita Fri Feb 11 15:31:15 2011
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="rrefproperlogboottrace" xml:lang="en-us">
+<title>derby.stream.error.logBootTrace</title>
+<prolog><metadata>
+<keywords><indexterm>derby.stream.error.logBootTrace</indexterm>
+<indexterm>Error log<indexterm>adding boot errors to</indexterm></indexterm>
+<indexterm>double-booting issues<indexterm>diagnosing</indexterm></indexterm></keywords>
+</metadata></prolog>
+<refbody>
+<section><title>Function</title>
+<p>Specifies whether boot errors are written to the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> log file.</p>
+<p>This property helps in diagnosing double-booting problems. Typically, when
+two Java Virtual Machines (JVMs) or class loaders attempt to boot
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, an error
+message like the following appears:</p>
+<codeblock>ERROR XJ040: Failed to start database 'testdb' with class loader 
+sun.misc.Launcher$AppClassLoader@481e481e, see the next exception for
+details.
+ERROR XSDB6: Another instance of Derby may have already booted the
+database C:\derby\testdb.</codeblock>
+<p>The message will also show the stack trace and class loader of the failed
+boot attempt. It is sometimes also useful to see the stack trace when the first
+successful boot attempt occurred. To see the stack trace of successful boots and
+shutdowns, set <i>derby.stream.error.logBootTrace=true</i> to trace the successful
+attempt. If you think that both attempts should be from the same class loader
+context, check also the class loader information for boot and shutdown attempts
+and make sure they all come from the same class loader context.</p>
+<p>For more information, see "Double-booting system behavior" in
+<ph conref="../conrefs.dita#pub/citdevelop"></ph>.</p>
+</section>
+<section><title>Default</title>
+<p>False.</p> </section>
+<example><title>Example</title>
+<codeblock><b>derby.stream.error.logBootTrace=true</b></codeblock>
+</example>
+<section><title>Scope</title>
+<p><xref href="crefproper51399.dita#crefproper51399/rrefproper41229">system-wide</xref></p>
+</section>
+<section><title>Dynamic or static</title>
+<p>This property is static; if you change it while
+<ph conref="../conrefs.dita#prod/productshortname"></ph> is running, the change
+does not take effect until you reboot.</p> </section>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/ref/rrefproperlogboottrace.dita
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message