-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Expose @JmsListener endpoint id to annotation-derived listener container (for transaction definition name) #26683
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
Labels
Milestone
Comments
As a side note, exposing the endpoint id also enables the listener container to use specific thread names based on that id, just like the bean name for a manually defined listener container is also showing up in the thread names (with the default task executor). |
This was referenced Mar 16, 2021
This was referenced Mar 17, 2021
Closed
lxbzmy
pushed a commit
to lxbzmy/spring-framework
that referenced
this issue
Mar 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Transaction name is always null when debug logging
@Transactional`` @JmsListener
methods.This chunk of code in
AbstractPollingMessageListenerContainer
returns null forgetBeanName():
It should be easy to support by setting the beanName from the endpoint passed into
createListenerContainer(JmsListenerEndpoint endpoint) { ... }
inAbstractJmsListenerContainerFactory
.The text was updated successfully, but these errors were encountered: