You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@jena.apache.org by rv...@apache.org on 2014/07/22 12:14:53 UTC

svn commit: r1612532 - /jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext

Author: rvesse
Date: Tue Jul 22 10:14:52 2014
New Revision: 1612532

URL: http://svn.apache.org/r1612532
Log:
Note inclusion of multi-JVM usage prevention from 1.1.0 onwards

Modified:
    jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext

Modified: jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext?rev=1612532&r1=1612531&r2=1612532&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/tdb_transactions.mdtext Tue Jul 22 10:14:52 2014
@@ -222,7 +222,8 @@ same storage but have independent transa
 Multiple applications, running in multiple JVMs, using the same
 file databases is not supported and has a high risk of data corruption.  Once corrupted a database cannot be repaired
 and must be rebuilt from the original source data. Therefore there **must** be a single JVM
-controlling the database directory and files.
+controlling the database directory and files.  From 1.1.0 onwards TDB includes automatic prevention against multi-JVM
+which prevents this under most circumstances.
 
 Use our [Fuseki](../serving_data/) component to provide a
 database server for multiple applications. Fuseki supports