AW: [opencms-dev] Clustering Opencms 6.2.2

[christian meyer]

Hi!

I hope i've understand you correctly. You have different Tomcat instances (maybe on different machines), without the Alkacon-Cluster-Component or maybe another Cluster component? 
If you press the "Clear Cache" Button or if you publish some stuff an event will fired clearing the local cache. This means in general the different Opencms-Instances doesn't know each other.
If you want to distribute an event to other system you've to add an Event-Listener listening to the publish event, sending this event to another CMS-Instance (e.g. via HTTP calling a special target page) and fire this event as a local event on the other machine (->OpenCms.fireEvent(iEventType) have a look on the API for more details).

Hope this will help a bit... 

Kind Regards 


Christian Meyer







-----Ursprüngliche Nachricht-----
Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Manuel Wallnoefer
Gesendet: Sonntag, 27. August 2006 17:31
An: 'The OpenCms mailing list'
Betreff: AW: [opencms-dev] Clustering Opencms 6.2.2


Hi,

no it doesn't solve the problem if i press the purge cache button !

Does anybody know how i can set a timeout for every page in the cache ?

I tried it to write timeout=10 in the cache property of every page but this doesnt work !

Is there any possibility to write cache directives in the template header or something like that ???

~manuel




-----Ursprüngliche Nachricht-----
Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Joe Desbonnet
Gesendet: Samstag, 26. August 2006 13:28
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] Clustering Opencms 6.2.2

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
>

_______________________________________________
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