Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Improve message sender / handler robustness in resync scenarios (#13733) (CP: 23.1) #13804

Merged
merged 1 commit into from
May 19, 2022

Conversation

vaadin-bot
Copy link
Collaborator

No description provided.

…13733)

Process re-sync messages via normal message queue and use semaphore to protect re-sync process (i.e. do not allow other messages while performing re-sync).

This PR is adopted from similar fixes for Vaadin 8.

vaadin/framework#11791
vaadin/framework#12043
vaadin/framework#12178

This also changes the method `forceMessageHandling` in a way that the desire to resynchronise is registered before calling `endRequest`. If this is not done, `endRequest` may end up sending out a request itself and that then causes the re-sync request to fail because a request is already in flight. This ends up throwing an IllegalStateException at com/vaadin/client/communication/RequestResponseTracker.java.

Fixes #13726

Co-authored-by: Artur <[email protected]>
Co-authored-by: Pepijn Van Eeckhoudt @pepijnve
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@vaadin-bot
Copy link
Collaborator Author

This PR is eligible for auto-merging policy, so it has been approved automatically.[Message is sent from bot]

@github-actions
Copy link

Unit Test Results

   964 files  ±0     964 suites  ±0   59m 49s ⏱️ + 4m 31s
6 276 tests ±0  6 227 ✔️ ±0  49 💤 ±0  0 ±0 
6 502 runs   - 2  6 447 ✔️  - 2  55 💤 ±0  0 ±0 

Results for commit bed4f01. ± Comparison against base commit 9c58563.

@mshabarov mshabarov merged commit 4cecdc4 into 23.1 May 19, 2022
@mshabarov mshabarov deleted the cherry-pick-13733-to-23.1-1652942043314 branch May 19, 2022 07:07
@vaadin-bot
Copy link
Collaborator Author

This ticket/PR has been released with Vaadin 23.1.0.rc1 and is also targeting the upcoming stable 23.1.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants