[MGNLCACHE-86] Cache stores broken pages when a database exception occurs while rendering Created: 09/Feb/15  Updated: 25/Mar/22

Status: Open
Project: Cache Modules
Component/s: None
Affects Version/s: 5.2.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Antoine Contal Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux RHEL 6, Oracle JDBC connector ojdbc6-12.1.0.1, Oracle Database 11g


Attachments: Text File magnolia_stack_trace.txt    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

While our Oracle database was unavailable due to an incident, the cache filled with pages with broken contents. After the incident was solved, the site still served broken pages because of the cache. A cache flush was required to fix the issue.

A better behavior would be to NOT cache a page if a low-level exception was raised during the rendering process.

The stacktrace of the database connection issue is attached to this JIRA issue.


Generated at Sun Feb 11 23:52:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.