Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Foundation 7, Foundation 8
-
8
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. Set /modules/publishing-core/config/receivers/demoPublic@readTimeout=30000 (30s) to save some time.
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.
Checklists
Attachments
Issue Links
- is duplicated by
-
EEPUBLISH-11 Read Timeout exception ends up with inconsistencies of content between public instances
-
- Closed
-