0046280: Full refresh should be executed every time there are model changes, but sometimes it doesn't happen

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #46280		[ All Revisions ] [ Back to Issue ]
Summary	0046280: Full refresh should be executed every time there are model changes, but sometimes it doesn't happen

Revision	2021-04-16 09:47 by marvintm
Steps To Reproduce	The combination of those two factors triggers the problem in the following way: - In a clean scenario we access the application. Hashes are saved correctly, and full refresh is done. Logout - We deploy a change in a model and restart Tomcat. - We access the application again. If the race-condition happens, we will check the hashes BEFORE the new hashes have been loaded. - In this case, we are missing the new hashes, so comparison is not done. However, the persisted hashes are OVERWRITTEN with the new hash structure (that is missing the backend hashes). At this point, we have lost the old hashes. As comparison is not done, full refresh is not done. - If we then refresh the page (or login/logout), then we finally load the new hashes, and compare them. As we are missing persisted backend hashes, we return no changes, but we still overwrite the persisted hashes, which means that we have set the new hashes in the persisted hashes. Full refresh is not done. At this point, we have completely lost the old hashes, new hashes have been persisted, but still, full refresh has not been done.

Revision	2021-04-16 09:44 by marvintm
Steps To Reproduce	The combination of those two factors triggers the problem in the following way: - In a clean scenario we access the application. Hashes are saved correctly, and full refresh is done. Logout - We deploy a change in a model and restart Tomcat. - We access the application again. If the race-condition happens, we will check the hashes BEFORE the new hashes have been loaded. - In this case, we are missing the new hashes, so comparison is not done. However, the persisted hashes are OVERWRITTEN with the new hash structure (that is missing the backend hashes). At this point, we have lost the old hashes. As comparison is not done, full refresh is not done. - If we then refresh the page (or login/logout), then we finally load the new hashes, and compare them. As we are missing persisted backend hashes, we return no changes, but we still overwrite the persisted hashes, which means that we have set the new hashes in the persisted hashes. Full refresh is not done. At this point, we have completely lost the old hashes, new hashes have been persisted, but still, full refresh has not been done.