We have moved to GitHub Issues
Created by Guy MacArthur 28 Apr 2015, 23:11:35 Updated by Peter Gregory 22 May 2015, 01:59:23
Accessing an Umbraco site while the database is unavailable resulted in a YSOD, but after the connectivity was restored the error remained. Clearing the browser cache did not fix the issue, nor did trying in a different browser. The only thing that did fix it was recycling the app (touching the web.config). We've just noticed this new behavior of caching the error after upgrading a client's site from 6.x to 7.2.1. They suffer from some network issues occasionally and the DB becomes inaccessible for a very brief time.
This has been retested in fresh 7.2.1, 7.2.4 and 7.2.5 RC installs. An easy way to demonstrate the behaviour is to take the DB offline and try to access the site. When it fails, bring the DB back online and try to access the site again. The same error persists.
What did you expect to happen? I expected the YSOD to occurr, however, once the connectivity was restored the error would go away and the site would work as per normal, as this has been the behaviour in version 6 and earlier.
Looks like this is fixed in this ticket: http://issues.umbraco.org/issue/U4-6597
On request from Guy.
Backwards Compatible: True
Affected versions: 7.2.4, 7.2.5
Due in version: