+1-888-365-2779
Try Now
More in this section

Forums / Deployment / SiteMapProvider and Webfarms

SiteMapProvider and Webfarms

3 posts, 0 answered
  1. Kurtis
    Kurtis avatar
    2 posts
    Registered:
    24 Jun 2009
    16 Jan 2010
    Link to this post
    I have built a new website for my job utilizing Sitefinity that has just been deployed to a clustered environment.  We have two servers which are both utilizing the same database.   I am noticing that when changes are made to page properties (page name, alternate urls, etc) or pages are removed from one server, the sitemap on the other server is not updated.  I have set cacheDependency="InDatabase" but this seems to have no effect on the sitemap data.  Is there any way to prevent the CmsSitemapProvider from caching or have it update based on changes in the database?

    Edit:  This is Sitefinity 3.7, SP2 if it helps.

    Thanks,

    Kurtis
  2. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    18 Jan 2010
    Link to this post
    Hi Kurtis,

    Thank you for posting your question. 

    By default, Sitefinity checks the cache state, which is in this case stored in the database, on every 1000ms. This means that there could be a slowdown on updating all the servers which is equal to 1000ms + the time for executing the db queries. I do not think this is the particular case though. 

    Can you please check both servers computer clocks? Since we are comparing the time, both servers should have approximately the same time.

    Other than that, the sitemap cache could not be disabled, but we do not have problem there, reported so far.

    Regards,
    Georgi
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. Kurtis
    Kurtis avatar
    2 posts
    Registered:
    24 Jun 2009
    20 Jan 2010
    Link to this post
    Georgi,

    Thanks, the times were the same but I figured it out. We had deployed our admin on a 32bit machine and our production websites on 64 bit machines. In case anyone else ever happens to run into this strange situtation, string.GetHashCode() returns different values on 32bit vs. 64bit hardware (as you would sort of expect) so the hashcodes stored in sf_DBCacheDependency were not working properly on the 64 bit hardware.  Turning on 32bit support in the IIS7 app pools resolved the issue.




Register for webinar
3 posts, 0 answered