While I don't know the source of this problem or the reason why it seems to be related to the upgrade, the mention of GetDescendents and large structures always makes me a bit worried. Make sure you use the references returned wisely, i.e. load batches of content items and process them, then drop the reference to those items. If you hold reference to huge amount of content at once, e.g. by loading all the content the references from GetDescendents point to into a list, you could run out of memory.
Is the code running as part of a web request? If so, it looks like the request timeout is hit, so the framework is aborting the request thread.
In addition to what Rahl said, can you use SQL Profiler to see which parameters were being called, and run the stored procedure directly against your DB in SQL Server Management Studio to see how long in take ?
Hi! Thanks for the responses. Sorry it took me so long to respond. It was definitely calling GetDescendents on the catalog root that was causing the issue. I ended up using Vulcan (elastic search scroll api) to build out the sitemap instead of the IContentLoader. Things are looking good now.
Hi,
I am stuck on this currently. Here is the stack trace. It is happening when GetDescendants is called on the root reference to my catalog:
The catalog is decently large at 40k products. I recently upgraded to latest versions of Episerver and started having this issue. We have a custom package for generating the sitemaps. I have also tried using the Geta Seo.Commerce.Sitemaps and I am not seeing that error, but, the job just runs forever and never generates anything. Here are the versions my app is running:
Any help would be greatly appreciated!
-John