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

Merge 2.0.x into 2.x #856

Merged
merged 9 commits into from
Oct 24, 2023
Merged

Merge 2.0.x into 2.x #856

merged 9 commits into from
Oct 24, 2023

Conversation

jansupol
Copy link
Contributor

No description provided.

dependabot bot and others added 9 commits June 14, 2023 15:26
Bumps [jetty-server](https://github.com/eclipse/jetty.project) from 9.4.41.v20210516 to 9.4.51.v20230217.
- [Release notes](https://github.com/eclipse/jetty.project/releases)
- [Commits](jetty/jetty.project@jetty-9.4.41.v20210516...jetty-9.4.51.v20230217)

---
updated-dependencies:
- dependency-name: org.eclipse.jetty:jetty-server
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
This issue may appear when 'send[data]' methods are triggered from different threads. As a result
threads race appears between cancelIdleTimeoutExecutor and scheduling new idle task.
Example of race:
1. Thread 1 cancels task
2. Thread 2 waits until thread 1 will finish
3. Thread 1 finishes
4. Thread 2 tries to cancel already cancelled task and leaves synchronized block
5. Thread 1 schedules new idle task
6. Thread 2 schedules another idle task, the first is overwritten and never cancelled.
As a result disconnection is triggered precisely after set idle timeout passes.

Signed-off-by: Mykyta Leonov <[email protected]>
Signed-off-by: jansupol <[email protected]>
@jansupol jansupol merged commit c0c732c into eclipse-ee4j:2.x Oct 24, 2023
3 checks passed
@jansupol jansupol deleted the r.214 branch October 24, 2023 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants