After a page update in CMS Server A, CMS Server A would send page cache update request to all other CMS servers via port 10082. Blocking port 10082 would prevent page cache synchronization in a CMS cluster environment. A quick review of the windows application logs would reveal exception error thrown by CMS when this is blocked.
Also, check the installation document for list of ports to open. I last saw it on the 11.2.1 installation manual. Also, I forgot where it is, either in server manager or project settings, set the publishing temp folder to a centralized UNC path. Else, each server will have its own temp publishing folder. On Thursday, September 11, 2014 4:00:44 AM UTC-4, Boris Crismancich wrote: > > Hi, > > I'm currently analyzing a strange behaviour. Maybe you have an idea or may > have come across the same problem: > > Cluster with 2 servers for editors and two for publication. > An editor changes a page and publishes it. The page is published, but its > content is not changed. > Logging on to the publication server, SmartEdit does not show the changes. > Clearing the PageCache solves the problem. > > So I guess, the PageCache sync does not work. > > Any ideas? > > Greetings from Hamburg, > Boris > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/d/optout.
