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

Propagate any existing server context into a Webclient reactive code (master) #3804

Merged
merged 1 commit into from
Jan 18, 2022

Conversation

spericas
Copy link
Member

This PR is about Helidon's context propagation to non-request threads (typically Netty threads). It makes the current context available to any reactive code handler in WebClient and also ensures context is propagated if req.next() is called inside Helidon in a different thread. Customer has verified that this PR fixes their application. See Issue #3734 for a discussion.

Signed-off-by: Santiago Pericasgeertsen santiago.pericasgeertsen@oracle.com

… It makes the current context available to any reactive code handler in WebClient and also ensures context is propagated if req.next() is called inside Helidon in a different thread.

Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
@spericas spericas added this to the 3.0.0 milestone Jan 13, 2022
@spericas spericas requested a review from danielkec January 13, 2022 15:50
@spericas spericas self-assigned this Jan 13, 2022
@spericas spericas merged commit 405716c into helidon-io:master Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants