Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Since the new paging model, where we don't keep paged messages for long as we used to keep, I'm going to remove the lazy application properties update done per ARTEMIS-3067.
Say a message is updated after decoded for whatever reason, it gets difficult to trace back to its original calculations.
I had already had issues in mirroring, and now it turns out that if you send a message in AMQP and receive with Core, and paging is involved the calculation will never return to 0 because the sizing might have been updated. and it's fairly difficult to trace back to when the message is going to leave the VM as it could still be referenced.
ARTEMIS-3067 alleviated some consequences of the page cache we used to have with the older model, but with the newer model this should not be an issue any longer. The remedy is having more consequences than intended anyways.
Attachments
Issue Links
- links to