Failed to Read cacheKey = 'EPSegmentData:68175:xxxx'
2. And try to increase Connection Timeout=30;
Thanks for the response. Unfortunatley your fix would not really solve the issue as the error shown was a symptom of what was going wrong rather than the cause of it (plus the bug you link to was fixed in CMS 10).
I have discovered this was an issue with one of our plugins/scheduled tasks which was making database calls within a Parallel.ForEach (bad!). This caused the code to fire off loads of simultaneous requests to the database and lock up the connection pool!
I discovered what was causing the issue by running a SQL Profile on the DB after firing the site up and tracing that back to the code.
I'm not sure why we only discovered this in testing but the job is scheduled to run at 5am (so I guess we never noticed) and I think the process of restoring DBs to the test environment meant the job had more rows to process than normal.
We have recently upgraded our version of EpiServer CMS from 7.5 to 11. It's mostly working fine but occasioanlly we get an issue where the site will take up all available connections on the database server, causing not only EpiServer to stop working but any other site that might be using that database server.
An example of the error we get is below but I suspect the entry is a syptom of the issue rather than the cause and it is never preceded in the logs by anything consistant. We don't get this issue in EpiServer 7.5 and the only changes we've made during the upgrade are those required as part of the upgrade.
Has anyone else experienced this following an upgrade? Is there an easy way to identify what could be causing the site to be using so many connections (it's definetly our EpiServer site as we have checked the database)? I suspected one of the internal scheduled jobs but short of disabiling them all and then starting them one by one I'm not sure how to identify which one?