-Original Message-
From: Marcel Reutegger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 02, 2006 7:23 PM
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
From what I understand the main issue remaining is how to enforce
cache
integrity
first read or write
operation.
Does this make sense you think?
-Original Message-
From: Marcel Reutegger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 03, 2006 5:12 PM
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
another idea would
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
Hi Marcel and the rest of the list,
please bear with me once more. I would like to ask if the following
scenario makes sense before applying it in practice.
Let's assume that I have 2 clustered
-Original Message-
From: Marcel Reutegger [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 11, 2006 12:25 PM
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
What I want to accomplish is let the other shisms know that the
persistent
@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
The question is the following. Let's assume I have some modified
itemstates from shism1 and want to propagate the changes to shism2.
If
we r talking about non-transient and non-local changes
cache.evict(id
-Original Message-
From: Marcel Reutegger [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 18, 2006 11:19 PM
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota Karadimitriou wrote:
Much obliged for your answer Marcel, things are starting to make
sense
Hi Giota,
Giota Karadimitriou wrote:
Hello,
I have finally put the scenario in action and so far I have
encountered
the following problems.
Regarding the actual scenario the problem I came across was in these
much discussed 2 lines of code :
//modifiedIt comes from shism1
In my previous email, I wrote the scenario that I try to follow
regarding clustering; however I feel I am really at zero once again so
could anybody provide me with some conceptual help regarding clustering
aspects because I feel I need to understand the jackrabbit model a lot
more in order to
I have been following up issue 313 and relative threads in order to try
to use a Datasource with a relative persistence manager.
My concerns are the following:
1) Regarding Marcel's comment:
Comment by Marcel
http://issues.apache.org/jira/secure/ViewProfile.jspa?name=mreutegg
Reutegger
First of all thanks a lot. Most of my questions were covered. Please
check my comments below:
-Original Message-
From: Marcel Reutegger [mailto:[EMAIL PROTECTED]
Sent: Friday, June 09, 2006 5:41 PM
To: dev@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
Giota
Hello,
I just applied the latest JCA changes commited by Edgar Poce related to
issues 412,461,462 and 463 and many thanks indeed because these problems
had been left open for quite a while.
However I now discovered after testing the following problematic
behaviour:
I will just describe it,
[
http://issues.apache.org/jira/browse/JCR-371?page=comments#action_12373098 ]
Giota Karadimitriou commented on JCR-371:
-
Just to add my experience on this, in case it helps:
This issue occured when while trying to perform concurrent versioning
12 matches
Mail list logo
