Return-Path:
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 24554 invoked from network); 13 Nov 2008 20:50:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
by minotaur.apache.org with SMTP; 13 Nov 2008 20:50:01 -0000
Received: (qmail 66407 invoked by uid 500); 13 Nov 2008 20:50:08 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 66383 invoked by uid 500); 13 Nov 2008 20:50:08 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
List-Post:
Reply-To: "Derby Development"
List-Id:
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 66374 invoked by uid 99); 13 Nov 2008 20:50:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2008 12:50:08 -0800
X-ASF-Spam-Status: No, hits=-1998.8 required=10.0
tests=ALL_TRUSTED,FS_REPLICA
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2008 20:48:56 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
id 334E7238898E; Thu, 13 Nov 2008 12:49:40 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r713816 - in /db/derby/docs/trunk/src/adminguide:
cadminlockvti83889.dita cadminreplication.dita cadminreplicfailures.dita
Date: Thu, 13 Nov 2008 20:49:40 -0000
To: derby-commits@db.apache.org
From: chaase3@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20081113204940.334E7238898E@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
Author: chaase3
Date: Thu Nov 13 12:49:39 2008
New Revision: 713816
URL: http://svn.apache.org/viewvc?rev=713816&view=rev
Log:
DERBY-2389: Move Derby system and properties info from Tuning Guide into Reference Manual
This patch fixes references to the system properties reference topics in the Administration Guide.
Patch: DERBY-2389-adminguide.diff
Modified:
db/derby/docs/trunk/src/adminguide/cadminlockvti83889.dita
db/derby/docs/trunk/src/adminguide/cadminreplication.dita
db/derby/docs/trunk/src/adminguide/cadminreplicfailures.dita
Modified: db/derby/docs/trunk/src/adminguide/cadminlockvti83889.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminlockvti83889.dita?rev=713816&r1=713815&r2=713816&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminlockvti83889.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminlockvti83889.dita Thu Nov 13 12:49:39 2008
@@ -20,31 +20,34 @@
"../dtd/concept.dtd">
Monitoring deadlocks
-The derby.stream.error.logSeverityLevel property determines the
+The derby.stream.error.logSeverityLevel property determines the
level of error that you are informed about.
derby.locks.deadlockTracederby.locks.monitor
derby.stream.error.logSeverityLevel
-By default, derby.stream.error.logSeverityLevel is
-set to 40000. If derby.stream.error.logSeverityLevel is
+
By default, derby.stream.error.logSeverityLevel is
+set to 40000. If derby.stream.error.logSeverityLevel is
set to display transaction-level errors (that is, if it is set to a value
-less than 40000), deadlock errors are logged to the derby.log file.
+less than 40000), deadlock errors are logged to the derby.log file.
If it is set to a value of 40000 or higher, deadlock errors are not logged
-to the derby.log file.
-The derby.locks.monitor property ensures that deadlock errors are
-logged regardless of the value of derby.stream.error.logSeverityLevel.
-When derby.locks.monitor is set to true, all
-locks that are involved in deadlocks are written to derby.log along with a unique
+to the derby.log file.
+The derby.locks.monitor property ensures that deadlock errors are
+logged regardless of the value of derby.stream.error.logSeverityLevel.
+When derby.locks.monitor is set to true, all
+locks that are involved in deadlocks are written to derby.log along with a unique
number that identifies the lock.
-To see a thread's stack trace when a lock is requested, set derby.locks.deadlockTrace to
-true. This property is ignored if derby.locks.monitor is
+
To see a thread's stack trace when a lock is requested, set derby.locks.deadlockTrace to
+true. This property is ignored if derby.locks.monitor is
set to false.
-Use derby.locks.deadlockTrace with care. Setting this property
+Use derby.locks.deadlockTrace with care. Setting this property
can alter the timing of the application, severely affect performance, and
-produce a very large derby.log file.
-For information about how to set properties, and information about the specific properties that are mentioned in this topic, see .
+produce a very large derby.log file.
+For information about how to set properties, see
+. For information about the
+specific properties that are mentioned in this topic, see the
+.
Here is an example of an error message when aborts
a transaction because of a deadlock:
--SQLException Caught--
@@ -58,7 +61,8 @@
Granted XID : {758, X} Lock : ROW, EMPLOYEE, (2,8)
Waiting XID : {758, U} , APP, update employee set bonus=150 where salary=23840
Granted XID : {752, X} The selected victim is XID : 752
-You can use the derby.locks.waitTimeout and derby.locks.deadlockTimeout properties
+You can use the derby.locks.waitTimeout and
+derby.locks.deadlockTimeout properties
to configure how long waits
for a lock to be released, or when to begin deadlock checking. For more information
about these properties, see the section that discusses controlling application
Modified: db/derby/docs/trunk/src/adminguide/cadminreplication.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminreplication.dita?rev=713816&r1=713815&r2=713816&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminreplication.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminreplication.dita Thu Nov 13 12:49:39 2008
@@ -90,8 +90,8 @@
Several Derby properties allow you to specify the size of the replication
log buffers and the intervals between log shipments, as well as whether
-replication messages are logged. See
- for details.
+replication messages are logged. See the
+ for details.
You can perform replication on a database that runs in either embedded mode
or Network Server mode.
Modified: db/derby/docs/trunk/src/adminguide/cadminreplicfailures.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminreplicfailures.dita?rev=713816&r1=713815&r2=713816&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminreplicfailures.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminreplicfailures.dita Thu Nov 13 12:49:39 2008
@@ -47,7 +47,7 @@
size limit before the connection can be reestablished, the master replication
functionality is stopped. You can use the property
derby.replication.logBufferSize to configure the size limit of the
-buffer; see for
+buffer; see the for
details.
@@ -96,7 +96,7 @@
increase for as long as log shipment has trouble keeping up with the amount of
generated log records. You can use properties to tune both the log buffer size
and the minimum and maximum interval between consecutive log shipments. See
- for details.
+the for details.
The slave