Return-Path: 
 <users-return-3235-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org
Received: (qmail 59605 invoked from network); 11 May 2007 08:49:02 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 11 May 2007 08:49:02 -0000
Received: (qmail 3118 invoked by uid 500); 11 May 2007 08:49:07 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 3103 invoked by uid 500); 11 May 2007 08:49:07 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:users@jackrabbit.apache.org>
List-Id: <users.jackrabbit.apache.org>
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Received: (qmail 3094 invoked by uid 99); 11 May 2007 08:49:07 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 01:49:07 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 01:49:00 -0700
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1HmQno-0004yJ-5A
	for users@jackrabbit.apache.org; Fri, 11 May 2007 01:48:40 -0700
Message-ID: <10428041.post@talk.nabble.com>
Date: Fri, 11 May 2007 01:48:40 -0700 (PDT)
From: dieter <lehmann.dieter@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: cluster only picking up changes on application restart
In-Reply-To: <10414902.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: lehmann.dieter@gmail.com
References: <10411053.post@talk.nabble.com>
 <66c10f230705100447j79191b4cme100958d7049c192@mail.gmail.com>
 <10412854.post@talk.nabble.com>
 <66c10f230705100652j483673c7j1f9b1a84c7a566@mail.gmail.com>
 <10414902.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


HI Dominique,

I have set my logging to INFO, but to not see any of the messages you
mentioned. My application is clearly not picking up the clustering so i will
have to delve a little deeper.

Thanks,

Dieter


dieter wrote:
> 
> Hi Dominique,
> 
> I don't see the log files growing at all.. in fact they have not even been
> created. I am not sure why this is happening. I guess i should start here.
> I will set the logging to INFO to see if i get any further info.
> 
> Dieter
> 
> 
> 
> Dominique Pfister wrote:
>> 
>> Hi Dieter,
>> 
>> your configuration looks fine to me, with
>> ${jackrabbit.journal.location} being the same physical path for every
>> instance, isn't it?
>> 
>> When making a change in one instance, you should see that the journal
>> file (located at ${jackrabbit.journal.location}/journal.log in your
>> setup) is growing. Can you verify that?
>> 
>> In every instance that is clustered, there is a file containing the
>> latest revision number, namely ${rep.home}/revision.log. Can you
>> verify, that, after having made some change in one instance and waited
>> for some delay (at most 5 seconds), the other instance has updated its
>> revision number file (check its last modified date)?
>> 
>> If that still doesn't help, I'd set the logging level to INFO. You
>> should then see some log message like the following:
>> 
>> *INFO * [...] AbstractJournal: Synchronized to revision: <some number>
>> 
>> in your other, passive instance after it has synchronized to the latest
>> change.
>> 
>> Hope this helps
>> Dominique
>> 
>> On 5/10/07, dieter <lehmann.dieter@gmail.com> wrote:
>>>
>>> Hi Dominique,
>>>
>>> Yes, i am pretty sure i have declared it properly, i basically just
>>> followed
>>> the guidelines in your wiki entry. I have it setup with a mysql database
>>> and
>>> each cluster id is unique.
>>>
>>> <Cluster id="local2">
>>>           <Journal
>>> class="org.apache.jackrabbit.core.journal.FileJournal">
>>>             <param name="revision" value="${rep.home}/revision.log" />
>>>             <param name="directory"
>>> value="${jackrabbit.journal.location}" />
>>>           </Journal>
>>>         </Cluster>
>>>
>>> Does it mean that the clustering is not working at all, or just working
>>> partially..?
>>>
>>> Dieter
>>>
>>>
>>> Dominique Pfister wrote:
>>> >
>>> > Hi Dieter,
>>> >
>>> > what does your repository.xml configuration file look like? Did you
>>> > properly declare the <Cluster> element?
>>> >
>>> > Kind regards
>>> > Dominique
>>> >
>>> > On 5/10/07, dieter <lehmann.dieter@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I have the same application running on two different web servers.
>>> When i
>>> >> add
>>> >> data to the one instance, it is not being picked up by the other
>>> instance
>>> >> until i restart the there application.
>>> >>
>>> >> Does anyone know where i have done wrong?
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/cluster-only-picking-up-changes-on-application-restart-tf3720933.html#a10411053
>>> >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/cluster-only-picking-up-changes-on-application-restart-tf3720933.html#a10412854
>>> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>>>
>>>
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/cluster-only-picking-up-changes-on-application-restart-tf3720933.html#a10428041
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.