Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 92431 invoked from network); 25 Jun 2008 13:16:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2008 13:16:22 -0000 Received: (qmail 64375 invoked by uid 500); 25 Jun 2008 13:16:21 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 64352 invoked by uid 500); 25 Jun 2008 13:16:21 -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 64341 invoked by uid 99); 25 Jun 2008 13:16:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 06:16:21 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jared.graber@iaccap.com designates 12.193.211.24 as permitted sender) Received: from [12.193.211.24] (HELO SITE3MAIL05.jeeves.ask.info) (12.193.211.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 13:15:32 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Multiple connections to database repository Date: Wed, 25 Jun 2008 09:15:27 -0400 Message-ID: In-Reply-To: <510143ac0806242154j2032c63bn49ce1a635d49507f@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Multiple connections to database repository Thread-Index: AcjWf5jwydCXp2sgT6q4kCxt/gXlWwARIQPw References: <7d3e1a010806241128j23ecfea3tc52cb7352df12510@mail.gmail.com> <510143ac0806242154j2032c63bn49ce1a635d49507f@mail.gmail.com> From: "Jared Graber" To: X-Virus-Checked: Checked by ClamAV on apache.org If possible I would prefer to stick with accessing the underlying database. Using RMI is an option but with the solution we're using, I see that as a potential problem as well. =20 In one of our environments, the repository will basically be read only - the database will overwritten with a copy from one of the other environments, but will restrict access to only reads. Because the data is being overwritten from an external source (not through the API) I can see that causing caching issues with RMI - unless the JCR-RMI server is restarted. In my apps, I don't need to have a constant connection to the repository backed by the database. I only need to connect when the app receives a signal to update its data (this doesn't happen often). Would shutting down the repository and reconnecting clear the cache? -Jared -----Original Message----- From: Jukka Zitting [mailto:jukka.zitting@gmail.com]=20 Sent: Wednesday, June 25, 2008 12:54 AM To: users@jackrabbit.apache.org Subject: Re: Multiple connections to database repository Hi, On Tue, Jun 24, 2008 at 11:07 PM, Jared Graber wrote: > In that case my question comes down to this: Are you decided about accessing the underlying database from multiple Jackrabbit clients from different host/JVMs? How about using JCR-RMI instead of a remote database connection to access the database. Then you wouldn't need to worry about any caching issues etc. BR, Jukka Zitting