Author: buildbot
Date: Tue Jul 22 10:43:44 2014
New Revision: 917085
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb/faqs.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 22 10:43:44 2014
@@ -1 +1 @@
-1612537
+1612541
Modified: websites/staging/jena/trunk/content/documentation/tdb/faqs.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb/faqs.html (original)
+++ websites/staging/jena/trunk/content/documentation/tdb/faqs.html Tue Jul 22
10:43:44 2014
@@ -243,11 +243,12 @@ system with a SSD you can always perform
<a href="#multi-jvm">Can I share a TDB dataset between multiple
applications?</a> question a TDB database can only be safely used by a single
JVM otherwise
data corruption may occur. From 1.1.0 onwards TDB automatically enforces this
restriction wherever possible and you will get this exception if you
attempt to access a database which is being accessed from another JVM.</p>
-<p>To investigate this error look use the process management tools for your OS
to see what the process ID referenced in the error is. If it is another JVM
-then the error is entirely valid and you should follow the advice about
sharing a TDB dataset between applications. In rare circumstances you may find
-that the process is entirely unrelated (this can happen due to stale lock
files since they are not always automatically cleared up) in which case you can
-try and manually remove the <code>tdb.lock</code> file from the database
directory. Please only do this if you are certain that the other process is
not accessing
-the TDB database.</p>
+<p>To investigate this error use the process management tools for your OS to
see what the process ID referenced in the error is. If it is another JVM
+then the error is entirely valid and you should follow the advice about
sharing a TDB dataset between applications. You may need to coordinate with
+the owner of the other process (if it is not yourself) in order to do this.</p>
+<p>In rare circumstances you may find that the process is entirely unrelated
(this can happen due to stale lock files since they are not always
automatically
+cleared up) in which case you can try and manually remove the
<code>tdb.lock</code> file from the database directory. Please only do this if
you are <strong>certain</strong> that
+the other process is not accessing the TDB database otherwise data corruption
may occur.</p>
<p><a name="no-lock-warning"></a></p>
<h2
id="i-see-a-warning-that-location-pathtodb-was-not-locked-if-another-jvm-accessed-this-location-simultaneously-data-corruption-may-have-occurred-in-my-logs">I
see a warning that <em>Location /path/to/db was not locked, if another JVM
accessed this location simultaneously data corruption may have occurred</em> in
my logs?</h2>
<p>This warning can occur in rare circumstances when TDB detects that you are
releasing a database location via <code>StoreConnection.release()</code> and
that the
