[EEPUBLISH-11] Read Timeout exception ends up with inconsistencies of content between public instances Created: 17/Aug/18 Updated: 29/Mar/22 Resolved: 02/Apr/19 |
|
| Status: | Closed |
| Project: | Publishing Transactional |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mercedes Iruela | Assignee: | Robert Šiška |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Epic Link: | Support | ||||||||||||
| Sprint: | Foundation 6, Foundation 7 | ||||||||||||
| Story Points: | 0 | ||||||||||||
| Team: | |||||||||||||
| Description |
|
If there is a Read Timeout exception when publishing in one of the public instances, the transaction is rolled back as expected. However, if after the timeout exception and the rollback the thread/resource is unblocked and the publication process continues, the content is published, and, as a result, the public instances end up with different content. To reproduce this issue. A Breakpoint can be added when the lock is done in one of the public instances (for example, info.magnolia.publishing.transactional.receiver.locking.TransactionalJcrLockManager.applyLock(Lock)). After the timeout exception is thrown, let the process continue and you will reproduce the issue. Can be reproduced in Magnolia 5.6.8 and 5.7.1. Read related support ticket for more information Due to high priority, release the module by itself. |
| Comments |
| Comment by Robert Šiška [ 01/Apr/19 ] |
|
The issue is fixed in the publishing-core module ( |
| Comment by Jan Haderka [ 02/Apr/19 ] |
|
Duplicates |