jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre" <mkwhita...@gmail.com>
Subject Re: Forcing a cluster synch
Date Fri, 19 Sep 2008 20:25:35 GMT
I think I might have found the answer to my own question with
RepositoryImpl.getClusterNode().sync().   However the getClusterNode()
api is only in the 1.5 SNAPSHOT and I'd prefer a solution that would
work in both the 1.4.x code stream since the release date of 1.5 is
unknown.  I also value anyone's opinions on whether this is the right
approach to solving this problem.  Thoughts?


On Fri, Sep 19, 2008 at 2:29 PM, Micah Whitacre <mkwhitacre@gmail.com> wrote:
> Hey All,
>  I have a situation where I have a round robin service (IBM HTTP
> Server), sitting atop the 3 JVMs (IBM Websphere Application Servers),
> and in each of those JVMs I have a RepositoryImpl connected to a
> shared database.  The repositories are clustered so that changes are
> propagated to the other JVMs.  Business logic calls are made into the
> round robin service and those calls are translated into various JCR
> calls.  The problem I have is that there are situations where changes
> made in one JVM haven't be applied to the other JVMs based on the
> cluster synchronization times.  Is there a way to force a cluster
> synchronization so that a JVM will ensure it is up to date?  Or
> perhaps a way to flush the cache?  Any reccommendations on ways to
> solve this problem?
> Thanks in advance for your help,
> Micah Whitacre

View raw message