Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 41979 invoked from network); 1 Jul 2008 21:14:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Jul 2008 21:14:07 -0000 Received: (qmail 65606 invoked by uid 500); 1 Jul 2008 21:14:07 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 65589 invoked by uid 500); 1 Jul 2008 21:14:07 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 65578 invoked by uid 99); 1 Jul 2008 21:14:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2008 14:14:07 -0700 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [12.193.211.24] (HELO SITE3MAIL05.jeeves.ask.info) (12.193.211.24) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2008 21:13:16 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8DBBF.459BE6F8" Subject: Jackrabbit Caching? Date: Tue, 1 Jul 2008 17:13:11 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Jackrabbit Caching? Thread-Index: Acjbv0SlxHPuKnZCSHCkIZLzxIR4qw== From: "Jared Graber" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C8DBBF.459BE6F8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a database backed repository that I want to export from (read only scenario) very infrequently (once on startup and when a method is called via JMX). =20 The problem that I am having is that the data in the repository can change behind the scenes (another app changes data in the repo, a database restore, or some other external action. When I re-export the data (after exporting it once already), it does not pick up the changes. I am assuming the nodes are cached behind the scenes (either in memory or the indices). I can't restart the application every time this happens and can't just use an RMI solution because the data might change with a database restore or something similar. =20 =20 Is the in-memory cache preventing me from getting the new data? If so: Is there a way to clear the cache programmatically? Is there a way to turn off caching? (This would work just as well in my case) Is it the indexing? If so: Is there a way to re-index programmatically?=20 =20 Any other suggestions? =20 -Jared ------_=_NextPart_001_01C8DBBF.459BE6F8--