Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 12804 invoked from network); 3 Mar 2009 09:06:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 09:06:35 -0000 Received: (qmail 34671 invoked by uid 500); 3 Mar 2009 09:06:34 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 34655 invoked by uid 500); 3 Mar 2009 09:06:34 -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 34644 invoked by uid 99); 3 Mar 2009 09:06:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 01:06:34 -0800 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 jukka.zitting@gmail.com designates 209.85.220.158 as permitted sender) Received: from [209.85.220.158] (HELO mail-fx0-f158.google.com) (209.85.220.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 09:06:27 +0000 Received: by fxm2 with SMTP id 2so2295264fxm.43 for ; Tue, 03 Mar 2009 01:06:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=u9czzDtWCJ1xa3twnumT/WCJ6cTl+woWFVqStgwJujI=; b=VPPjKXZx9PUrjCpolr75eZWJ7d3f2SjrSidqkDPFKHu3gav1nOVEN6ZPx7WsYRBTf4 JyEwM1kcLUYw7zlipzPjHyIRUL96CTABQiDEcFEPkofUF5yCvbbMtBFNr7POJ2Ej3W5H NHfIOeRJAFEt9Rkw53dhd+r7GUTjs3GaimPpg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=hL4VxPR3tmCjSkbC2ujJ45tr45L5iGSAJgV8tUi2sztjiwM3CXZQSx/HHG35j+pFqd FzwoOGR/SNak9jQYA84FnoHC8YUHCtsXh3Y0C0aMf8BfnOXKR4ccATkAPFgf4kPFHuju qwMCydDQOXfJqfJBLl4lnsIRGevCngRDeFsXU= MIME-Version: 1.0 Received: by 10.181.215.9 with SMTP id s9mr2459826bkq.212.1236071166025; Tue, 03 Mar 2009 01:06:06 -0800 (PST) In-Reply-To: References: Date: Tue, 3 Mar 2009 10:06:05 +0100 Message-ID: <510143ac0903030106v76e1e77ev8c6c60e6b69d8f7@mail.gmail.com> Subject: Re: standalone server scenario From: Jukka Zitting To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Tue, Mar 3, 2009 at 1:32 AM, cifroes wrote: > My app has high scalability needs so I'm using 2 Jboss instances in 2 servers > (with a load balancer upfront). Now I want to add a Jackrabbit repository to my > app but, from what I understand I can't use the JNDI / "Shared J2EE Resource" > deployment model. In fact you can, and for high scalability needs it's actually recommended that you run Jackrabbit locally on each cluster node. To do this you simply need to configure Jackrabbit as a cluster. See http://wiki.apache.org/jackrabbit/Clustering for the details. > Is the solution for this problem the usage of the standalone jackrabbit server > and connecting to it by RMI? Does that have any problem in a production > environment (is it much slower, etc?)? RMI access is notably slower than local access, so I wouldn't recommend it for performance-sensitive deployments. > 2) http://wiki.apache.org/jackrabbit/JackrabbitOnJBoss mentions jcr-rmi to > expose jackrabbit via RMI but that doesn't seem to be available to download > to Jackrabbit v.1.5.x, why is that? The pre-built jackrabbit-jcr-rmi jar can be found on the central Maven repository. Or you can pick it from within WEB-INF/lib of the jackrabbit-webapp war file. BR, Jukka Zitting