db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1550425 - in /db/derby/docs/trunk/src: ref/rrefproperstatementcachesize.dita tuning/ctundepth32379.dita
Date Thu, 12 Dec 2013 14:26:12 GMT
Author: chaase3
Date: Thu Dec 12 14:26:12 2013
New Revision: 1550425

URL: http://svn.apache.org/r1550425
DERBY-4280  Property not documented - derby.language.statementCacheSize

Modified a Reference Manual topic and a Tuning Derby topic.

Patch: DERBY-4280-3.diff


Modified: db/derby/docs/trunk/src/ref/rrefproperstatementcachesize.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefproperstatementcachesize.dita?rev=1550425&r1=1550424&r2=1550425&view=diff
--- db/derby/docs/trunk/src/ref/rrefproperstatementcachesize.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefproperstatementcachesize.dita Thu Dec 12 14:26:12 2013
@@ -36,9 +36,6 @@ cache. Consider raising this number if s
 <p>For more information on the statement cache, see "Using the statement cache"
 in <ph conref="../conrefs.dita#pub/cittuning"></ph>.</p>
-<p>Set this property to zero if you find that deadlocks are occurring when
-prepared statements become outdated. These deadlocks can happen in
-multi-threaded applications that alternate selects and updates.</p>
 <p>100 statements.</p>

Modified: db/derby/docs/trunk/src/tuning/ctundepth32379.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctundepth32379.dita?rev=1550425&r1=1550424&r2=1550425&view=diff
--- db/derby/docs/trunk/src/tuning/ctundepth32379.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctundepth32379.dita Thu Dec 12 14:26:12 2013
@@ -86,10 +86,5 @@ precompiled statements which
 cache. Consider raising this number if statement preparation is taking too much
 time. See the <ph conref="../conrefs.dita#pub/citref"></ph> for more information
 on this property.</p>
-<p>A multithreaded database application that frequently alternates select and
-update statements can encounter deadlocks when a prepared statement becomes
-invalid or outdated. If your application becomes deadlocked under these
-circumstances, you can work around this problem by setting the value of the
-<i>derby.language.statementCacheSize</i> property to zero.</p>

View raw message