Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 53962 invoked from network); 27 Aug 2007 12:25:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Aug 2007 12:25:43 -0000 Received: (qmail 98847 invoked by uid 500); 27 Aug 2007 12:25:38 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 98830 invoked by uid 500); 27 Aug 2007 12:25:38 -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 98821 invoked by uid 99); 27 Aug 2007 12:25:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2007 05:25:38 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mwaschkowski@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2007 12:25:31 +0000 Received: by py-out-1112.google.com with SMTP id u77so1009119pyb for ; Mon, 27 Aug 2007 05:25:10 -0700 (PDT) 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:references; b=Kkx/P/xBWGxFhqmus1UzzxWXWjKi0rD2fIxvUpjhABU8ulE/K3zysFtMzLH208B2bcX4c3M/KwRPGKuY5TmmAzkb+ib8r8fQABHo0fsX3j7WHSkuVJgoMCCJBfbfYI/ixElebOrUeQ9Yh/tpZ6kVve15yQAbzuOEelsUsi/VfrQ= 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:references; b=YuX4kXyC4D0oN7vplWaFzxrZPv0BkYNmxj8YH9rXdbeW6rfyXCiPDkcNWAB2pY5CbF9bpQ7yomTdlfAzn8uUCZwIWVaxg69AnnXNj+zZTYKnoohbHKPWR+D/V0rBZmjJzcWZ9YSbb5Q0cQLLXZVVrASsIiYxiCvLKkK3+NeTrW4= Received: by 10.65.114.11 with SMTP id r11mr10681321qbm.1188217509396; Mon, 27 Aug 2007 05:25:09 -0700 (PDT) Received: by 10.65.141.7 with HTTP; Mon, 27 Aug 2007 05:25:09 -0700 (PDT) Message-ID: <76a6ebd00708270525h74a538ccv5d1b838d866f6dc0@mail.gmail.com> Date: Mon, 27 Aug 2007 08:25:09 -0400 From: "Mark Waschkowski" To: users@jackrabbit.apache.org Subject: Re: Problem with RMI, JBOSS reconnect issues, application session getting null In-Reply-To: <12299402.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_138826_7691806.1188217509327" References: <12299402.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_138826_7691806.1188217509327 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Sudhan, I'm not a jackrabbit dev, just a user, but wanted to let you know my thoughts since nobody else has responded yet. The behavior that you have seen is expected given the type of implementation that jackrabbit has, based on the original spec. IMHO, given the way jackrabbit is implemented currently, your situation/architecture is problematic for robust event listening. In jackrabbit 1.x the session that was used to register an event listener MUST stay open for those event listeners to work. ie. you must keep a listener session open for the lifetime of the application. This is obviously a huge problem if a connection is lost, even temporarily, when there doesn't appear to be any mechanism to reconnect a session. A confirmation of this from the devs would be appreciated. This isn't the most robust way to do facilitate observation, an improved version would involve the jackrabbit system itself managing listeners once registered (ie. not being bound to a particular session). It looks to me like the next version of the spec points to this (through journaling), although the spec is still in development, so we'll have to wait and see. Of course, if you follow a model - 2 deployment approach, embedding jcr within the server, then you won't have these kinds of issues. Sorry that the doesn't appear to be an existing solution to your problem. Best, Mark On 8/23/07, Sudhan wrote: > > > Hi, > > I have an application which runs on JBoss and connects to Jackrabbit > repository through RMI(We have also deployed jackrabbit - webapp war > inside > same instance of JBoss, ie. on local machine). Now my problem starts when > I > unplug the network cable and after 5-6 seconds plug it back to the network > my application Session gets destroyed. This is because i am registering > Node_Added and Node_Deleted events by implementing > javax.jcr.observation.EventListener in my application. > > I can access the repository through DAVExplorer aswell as our customised > GUI. Now when i create a new node it gets added to the repository and but > my > Class which is implementing EventListener interface is not able to listen > to any of these events. > > The likely reason seems to me is that, the session it used before > unplugging > is no longer available and thus there are no listeners registered after > unplug. And these behavior does not improve after re-plugging it back. > Meaning the session object is still null and thus cannot listen to any > events registered before. > > I am using org.springmodules.jcr.JcrSessionFactory to get my session. Now > can somebody help me in resolving this problem or point me if i am doing > something wrong. > > thanks for your support. > > Sudhan > -- > View this message in context: > http://www.nabble.com/Problem-with-RMI%2C-JBOSS-reconnect-issues%2C-application-session-getting-null-tf4319183.html#a12299402 > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > > -- Best, Mark Waschkowski ------=_Part_138826_7691806.1188217509327--