[MGNLADVCACHE-120] Cache shows issues when using personalization Created: 27/Apr/22 Updated: 27/Apr/22 Resolved: 27/Apr/22 |
|
| Status: | Closed |
| Project: | Advanced Cache |
| Component/s: | personalization |
| Affects Version/s: | 2.3.4 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Roberto Gaona | Assignee: | Roman Kovařík |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | author-experience | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Team: |
| Description |
|
According to SUPPORT-14566, when using Ehcache3, errors related to any personalized content appears on the logs (MgnlLockTimeout). When changing the personalization specific classes back to the default ones, the errors disappeared and the cache worked without complications. This makes us think that there may be issues with the cache when using personalization and should get investigated. |
| Comments |
| Comment by Roberto Gaona [ 27/Apr/22 ] |
|
I opened it on the wrong project, I am creating it on Personalization better. |