[opencms-dev] Clustering Opencms 6.2.2

Cayetano hnzekto at gmail.com
Sat Aug 26 10:32:54 CEST 2006


>
> 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



More information about the opencms-dev mailing list