jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dieter <lehmann.die...@gmail.com>
Subject Re: cluster only picking up changes on application restart
Date Fri, 11 May 2007 08:48:40 GMT

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.


Mime
View raw message