Thread name prefix is not always set when using virtual threads #39958
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
…irtual threads. 2. Added tests for it.
spring-projects-issues
added
the
status: waiting-for-triage
mhalbritter
changed the title
mhalbritter
added
type: bug
This was referenced Mar 18, 2024
mhalbritter
pushed a commit
that referenced
this pull request
Mar 18, 2024
mhalbritter
added a commit
that referenced
this pull request
Mar 18, 2024
|
I see. You guys prefer that way. Got it. |
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.
Currently the thread names are missing for rabbit listener, pulsars' consumer and task executor.
This PR added the thread names for mentioned components following convention specified in other autoconfigs via RabbitAnnotationDrivenConfiguration and PulsarAutoconfiguration.
Tests are added as well to check the threads names are specified when threads are created (via java.util.concurrent.ThreadFactory#newThread) through the factory.
Request / bug ticket, #39748