[opencms-dev] Clustering Opencms 6.2.2

[Joe Desbonnet]

If you go to the administration screen, choose FlexCache and press the
purge cache button, does it solve the problem?

If so it may be possible allow remote triggering of the purge cache
mechanism. Of course this would temporarily place extra load on the
servers while the pages are regenerated.

Joe.



On 8/26/06, Manuel Wallnoefer <manuel.wallnoefer at msk-informatik.at> wrote:
> Hi Cayetano,
>
> thx for your help !
>
> But i don't work with static export, and i have found the "real" problem
> right now.
>
> The "real" problem is the flex Cache.
>
> Because when i restart all my tomcat instances all of them are up to date !
>
> And i tried to enable the flex cache in the opencms-system.xml and then it
> works fine!
>
> But the problem is that the site where i use the cluster is under heavy load
> and i think when i turn off the flex cache , ill get a bad performance !
>
>
> I tried to stet the property cache of each site to timeout=20 to reload the
> cache every 20 minutes, but it doesn't work !!
>
> Can anybody help me out !!
>
> Thx !
>
> ~manuel
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: opencms-dev-bounces at opencms.org
> [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Cayetano
> Gesendet: Samstag, 26. August 2006 10:33
> An: The OpenCms mailing list
> Betreff: Re: [opencms-dev] Clustering Opencms 6.2.2
>
> >
> > But if i log in to the workplace and do sone changes to one file and
> publish
> > the file, the changes are only visible on that instance where i logged
> into
> > the workplace.
> >
> > The change is saved in the db because when i log into the workplace on
> > another instance i can see it in the backoffice view!
> >
> > Then i must touch the file and publish it again, and now on the second
> > instance i can see the change !
> >
> > So i had to do this for every instance, to see the change all the time !
> >
> > What it wrong with my clustered installation.
> >
>
> Nothing, probably the problem is about static export,which it's only
> executed on the instance where you created the content and then you
> have to "export" on every instance, a solution for this could be used
> the scheduled job: org.opencms.scheduler.jobs.CmsStaticExportJob to
> force a static export every XX minutes (which is a bit waste of
> resources) or maybe i think on a webservices api on every instance to
> synchronize the static export when a content is created. I suppose
> that the OCEE solves the synchronization problem.
>
> Hope that helps
> --
> Cayetano
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>