[MAGNOLIA-2677] Caching big content may cause OutOfMemoryError Created: 02/Apr/09 Updated: 11/May/11 Resolved: 01/Dec/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | cache |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | 4.4 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Henryk Paluch | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cache, outofmemoryerror | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 3.6.3 CE |
||
| Issue Links: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
Serving big binary node data (>100MB) may cause OOM error when server doesn't have enough of the memory assigned. This issue is due to the nature of objects in EhCache - cached objects are required to be Java objects, which are then serialized and kept in memory or in file system by the cache itself. NOTE: this error occurs on Public instances only, whose has caching enabled and heap size is small (relative to size of data served)! How to reproduce: java.lang.OutOfMemoryError: Java heap space Woraround: add voter to cache policy to avoid caching of big data or disable caching |
| Comments |
| Comment by Philipp Bärfuss [ 23/Nov/10 ] |
|
Going to use a threshold caching stream which will serve bigger files from the repository |