From users-return-1778-apmail-directory-users-archive=directory.apache.org@directory.apache.org Fri Sep 12 17:51:22 2008 Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 7250 invoked from network); 12 Sep 2008 17:51:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Sep 2008 17:51:22 -0000 Received: (qmail 7029 invoked by uid 500); 12 Sep 2008 17:51:19 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 6873 invoked by uid 500); 12 Sep 2008 17:51:19 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 6862 invoked by uid 99); 12 Sep 2008 17:51:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 10:51:19 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 76.96.30.64 is neither permitted nor denied by domain of rich@remingtons.us) Received: from [76.96.30.64] (HELO QMTA07.emeryville.ca.mail.comcast.net) (76.96.30.64) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 17:50:19 +0000 Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA07.emeryville.ca.mail.comcast.net with comcast id Dt0A1a0020EPchoA7tqhvX; Fri, 12 Sep 2008 17:50:41 +0000 Received: from BigMac.local ([75.71.40.223]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id Dtqf1a00F4ot8aK8Mtqgsa; Fri, 12 Sep 2008 17:50:40 +0000 X-Authority-Analysis: v=1.0 c=1 a=E4zk51m0QpNUTiTFW_oA:9 a=Ykn6Z1MDLI63l7ZAkzPHGH7YO3AA:4 a=XF7b4UCPwd8A:10 Message-ID: <48CAABEF.1070908@remingtons.us> Date: Fri, 12 Sep 2008 11:50:39 -0600 From: Rich Remington User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: weird caching behavior? References: <48CA686F.9090307@remingtons.us> <48CA6A7E.1060209@nextury.com> <48CA96FB.7000209@remingtons.us> <48CA9904.5090200@nextury.com> In-Reply-To: <48CA9904.5090200@nextury.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thanks for the feedback! It appears that I need to try the upgrade as I do have the synchOnWrite=true already. Where can I find 1.5.4 today? Also, I am still confused about the scenario I am experiencing. The webapp is the one responsible for making the password change, which is then seen by the Studio app right afterward. So, if the cache has the change, it seems that the cache should be used for future bind requests by either the webapp or Studio. It really shouldn't matter if it has hit the disk yet, should it? Cheers, Rich Emmanuel Lecharny wrote: > Rich Remington wrote: >> I am running Mac OSX. The file system write issue does not make >> sense to me if I can see the change has occurred using Apache Dir >> Studio before the reboot. > The problem is that you are still hitting the cache :) So it does not > prove anything ... >> I *could* try the upgrade to 1.5.3, but *should* I? How stable is >> that version compared to 1.5.3? > We are just releasing 1.5.4 today (the announcement is not yet done, > but will be tomorrow). So, yes, you *should*, becuase 1.5.x is way > better than 1.0.x. >> >> Just a thought... if the webapp (Spring Security) pools the >> connection and keeps it alive with the old password, could that >> explain the scenario? > Hmmmm. I don't know... If you stop the server, start it again, and you > don't see the password using Studio, then that mean the password has > not been saved on disk. >> I am not positive that a new bind request is actually flowing to >> Apache DS - can I see all bind attempts in the log file? > You have to set the logs to the correct level to get such an information. >