I have a client running a website in Umbraco 4.5.2 and they seem to have an issue where by an XSLT macro is occasionally returning blank when caching is enabled.
Strangley, if they have "Cache By Page" enabled and "Cache Personalized" disabled, then the macro are sometimes return blank values. Enabling "Cache Personalized" fixes the issue.
Anyone seen this before? / any ideas I can suggest?
Hmm, I was seeing these problems on 4.9 but only when the site ran under load. The load only needed to be small ~3 concurrent users.
Essentially I'm caching a macro that's a .NET Custom Control that in turn calls rendertemplate. When the app warmed up under load I was seeing either no text output or the control would have been called a number of times before committing back to the cache so you would see the same HTML repeated a number of times.
In the end I added a custom cache layer as it seemed the server.execute call from within rendertemplate was causing problems.
Cached Macros Returning Blank
Hi Guys,
I have a client running a website in Umbraco 4.5.2 and they seem to have an issue where by an XSLT macro is occasionally returning blank when caching is enabled.
Strangley, if they have "Cache By Page" enabled and "Cache Personalized" disabled, then the macro are
sometimes return blank values. Enabling "Cache Personalized" fixes the issue.
Anyone seen this before? / any ideas I can suggest?
Cheers
Matt
Been there, done that, an upgrade to 4.7.2 has fixed it for us... It IS documented somewhere, just can't find it atm.
It's a really inconsistent bug which is really hard to repro. Anyway, an upgrade will fix it! Promise.
Cheers,
/Dirk
Ok, I found another post so ignore my last post, an upgrade to 4.7.1(.1) should fix it!
Cheers,
/Dirk
Hmm, I was seeing these problems on 4.9 but only when the site ran under load. The load only needed to be small ~3 concurrent users.
Essentially I'm caching a macro that's a .NET Custom Control that in turn calls rendertemplate. When the app warmed up under load I was seeing either no text output or the control would have been called a number of times before committing back to the cache so you would see the same HTML repeated a number of times.
In the end I added a custom cache layer as it seemed the server.execute call from within rendertemplate was causing problems.
Cheers,
Chris
Is is the same problem as in this topic? http://our.umbraco.org/forum/developers/api-questions/8584-Severe-Issue-with-macro-caching-under-heavy-load
Should be fixed: http://umbraco.codeplex.com/SourceControl/network/forks/florisrobbemont/MacroCachingHeavyLoadPart2/contribution/3018
Jeroen
Cool, cheers guys. The client is in the process of upgrading to 4.11 anyway, so I've said they should retest after the upgrade.
Matt
is working on a reply...