Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 90737 invoked from network); 1 Mar 2007 08:57:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Mar 2007 08:57:32 -0000 Received: (qmail 45205 invoked by uid 500); 1 Mar 2007 08:57:39 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 45192 invoked by uid 500); 1 Mar 2007 08:57:39 -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 45183 invoked by uid 99); 1 Mar 2007 08:57:39 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 00:57:39 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 00:57:28 -0800 Received: by nf-out-0910.google.com with SMTP id x4so846994nfb for ; Thu, 01 Mar 2007 00:57:07 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TIEmefir+KD8TWA6owoYrkdnDJO9Iw7YMB+sHrgEJVbZCfvcVlEowf0XhlVkC95VYI5vxo5QCA1pj7/QjMKnzFYv3CVDfMzf28vc+MkscQ2nZhw1uEEycExlwyKTsv7s3E7EtHoX4RxRF+QTcy8Jz9WBs4Qmu9qR+BBsHlie1BY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sD+gHN+3HGNu6nEj/L5GpEvNnPgAC21RHsXGjn5oBlq0IDPStSBXeWNZtL06dujLmFKFTCSL9dwKA4RElA0HJaeZGyrtO/9GhuW9x2a9toO0zvTWiUP6RMa55z9piIYzjHH9R9K9+LEfrspimZ6g3QVToxj1txKiBI2FUzTe6b4= Received: by 10.78.172.20 with SMTP id u20mr139959hue.1172739426393; Thu, 01 Mar 2007 00:57:06 -0800 (PST) Received: by 10.78.106.19 with HTTP; Thu, 1 Mar 2007 00:57:06 -0800 (PST) Message-ID: <510143ac0703010057y59c79e0w8bf9af5c08bf9c60@mail.gmail.com> Date: Thu, 1 Mar 2007 10:57:06 +0200 From: "Jukka Zitting" To: users@jackrabbit.apache.org Subject: Re: how to shutdown a remote repository In-Reply-To: <45E566BD.8000505@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E566BD.8000505@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 2/28/07, ruchi goel wrote: > *But here RemoteRepository does not have a method to shutdown !! > > Is there some other way to shutdown the repository ?* No, the RMI layer currently does not expose the shutdown() method. The reason for this was that the responsibility of stopping the repository should be on the component that started it in the first place, not on some remote client. It is a separate question on whether that component want's to expose some mechanism (perhaps another RMI interface) for remote clients to request repository shutdown. One alternative you might want to consider is to use TransientRepository as the repository that's gets bound remotely. The TransientRepository class automatically shuts down the repository when there are no active sessions connected to it. BR, Jukka Zitting