Home/ Questions/Q 7015271
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T22:37:49+00:00

We have two production servers for Sitecore, one CM i.e. Content Management and another

  • 0

We have two production servers for Sitecore, one CM i.e. Content Management and another is CD i.e. Content Delivery. CM is refering to WEB, Core and Master. CD is refering to Core and Web. When we create a new content and publlish it to Web database, it is not available to CD server right away. To have that content available on CD server right away, we need to recyle application pool by adding and removing space in web.config.

Is there any way we can make a content available to CD server right away without recycling our application pool?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From the symptoms you describe I would say the the caches on the front-end (CD) server are not being cleared on publish and so you are seeing old content. As you are using 6.4 you will need to enable ‘Event Queues’. This means that when you publish, an event is sent to the front-end web boxes telling it to clear the caches and refresh your content.

    The short answer is to enable the include found in /App_Config/Include/ScalabilitySettings.config (rename from .example) on the CD and CM servers but it is worth understanding what is going on and how this mechanism works in case you have to diagnose further.

    Intro here : http://www.sitecore.net/Community/Technical-Blogs/Getting-to-Know-Sitecore/Posts/2010/07/Introducing-the-Sitecore-Event-Queue.aspx

    The documentation for this can be found here : http://sdn.sitecore.net/Reference/Sitecore%206/Scaling%20Guide.aspx

    Hope this helps 🙂

    • 0