#5717 - Nima WebServer.stop() is slow / not timely when there are no active requests #5748
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch current has 2 tests and 2 approaches to solving this issue.
The latest commit solves the issue using a modified/hacked version of
ThreadPerTaskExecutor
and a new interfaceInterruptibleTask
(and this approaches points to trying to get a similar change to the JDK).The prior solution used application code to maintain the active
Http1Connection
which duplicates functionality ofThreadPerTaskExecutor
and as such doesn't appeal as an elegant solution.