[WFLY-14748] Allow configuration of default async context timeout in configs #673
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
stability-level/preview
ropalka
changed the title
ropalka
changed the title
darranl
reviewed
Dec 17, 2024
|
|
||
| == Overview | ||
|
|
||
| At present the default asynchronous context timeout for Undertow asynchronous operations is hard coded. |
There was a problem hiding this comment.
When you say "the default" is there a second mechanism they can use to set the timeout?
There was a problem hiding this comment.
Yes @darranl it is via io.undertow.servlet.api.DeploymentInfo.setDefaultAsyncContextTimeout()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://issues.redhat.com/browse/WFLY-14748
Add analysis document
Resolves #672