Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <18124510.1154256674767.JavaMail.jira@brutus>
Date: Sun, 30 Jul 2006 03:51:14 -0700 (PDT)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-685) Modification on an entry should
 always be flushed to the disk
In-Reply-To: <7095736.1154256433900.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIRSERVER-685?page=comments#action_12424375 ] 
            
Emmanuel Lecharny commented on DIRSERVER-685:
---------------------------------------------

In fact, there is an existing flag (synchOnWrite) which has been created to implement this behavious, but it's always set to false, so we never have synchornization on write. 

This flag should be set to true by default, and the server.xml configuration may contains a way to modify this value to false (even if this seems obviously dangerous to do so ...)

> Modification on an entry should always be flushed to the disk
> -------------------------------------------------------------
>
>                 Key: DIRSERVER-685
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-685
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>
> When modifying an entry, we should always flush this entry to the disk.
> The JDBM backend, AFAIK, only update its cache, and a thread flush those caches periodicaly. However, I may be wrong (and I hope to be wrong :)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira