db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From myrn...@apache.org
Subject svn commit: r1640644 - /db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
Date Wed, 19 Nov 2014 23:52:08 GMT
Author: myrnavl
Date: Wed Nov 19 23:52:08 2014
New Revision: 1640644

URL: http://svn.apache.org/r1640644
Log:
DERBY-600; Document that DB is booted in read-only mode if not able to create db.lck file
   Modifying cdevdvlp20458.dita to reflect this behavior. 

Modified:
    db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita?rev=1640644&r1=1640643&r2=1640644&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita Wed Nov 19 23:52:08 2014
@@ -39,6 +39,7 @@ diagnosing a double boot problem, use th
 <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 Derby is not able to create the <i>db.lck</i> file when booting a
database, the database will be booted in read-only mode. This may happen due to lack of disk
space or access rights for the database directory. The boot message in the <i>derby.log</i>
will state that the database has been booted in READ ONLY mode. See also <xref href="cdevdeploy15325.dita#cdevdeploy15325"></xref>.</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



Mime
View raw message