Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 37091 invoked from network); 29 Sep 2010 12:14:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Sep 2010 12:14:04 -0000 Received: (qmail 62146 invoked by uid 500); 29 Sep 2010 12:14:04 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 61984 invoked by uid 500); 29 Sep 2010 12:14:02 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 61977 invoked by uid 99); 29 Sep 2010 12:14:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Sep 2010 12:14:01 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aklimets@day.com designates 207.126.148.87 as permitted sender) Received: from [207.126.148.87] (HELO eu3sys201aog101.obsmtp.com) (207.126.148.87) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 29 Sep 2010 12:13:54 +0000 Received: from source ([209.85.215.176]) by eu3sys201aob101.postini.com ([207.126.154.11]) with SMTP ID DSNKTKMtbInkv38LnlqkOfgDRf7TkZcGCQWs@postini.com; Wed, 29 Sep 2010 12:13:33 UTC Received: by eyg5 with SMTP id 5so244387eyg.35 for ; Wed, 29 Sep 2010 05:13:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.56.17 with SMTP id w17mr1234469ebg.76.1285762412721; Wed, 29 Sep 2010 05:13:32 -0700 (PDT) Received: by 10.14.53.75 with HTTP; Wed, 29 Sep 2010 05:13:32 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 Sep 2010 14:13:32 +0200 Message-ID: Subject: Re: In deph Jackrabbit clustering question From: Alexander Klimetschek To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Sep 29, 2010 at 13:42, William Ribeiro wrote: > Anyway ... I can't understand how this mechanism works. I need to find the > method that invokes the PersistenceManager for persisting the new items > found in the Journal's records. Why? The writing cluster node will a) store the new node in the persistence manager and then b) notify the journal of the change. This propagates to the other nodes, which can then invalidate their cache. The persistence manager on those other nodes must be able to retrieve the new/changed node then (immediately). Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com