Tracing information is missing when Exception is thrown from JmsListener methods #26532
Labels
in: messaging
Issues in messaging modules (jms, messaging)
status: superseded
An issue that has been superseded by another
Comments
spring-projects-issues
added
the
status: waiting-for-triage
|
This is superseded by #30335 |
bclozel
added
status: superseded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affects: 5.3.3
The issue was originally reported for Spring Cloud Sleuth but it seems it is not a Sleuth issue (and I can't transfer issues across orgs) so I'm opening this one to track it at the right place.
The original issue is this: spring-cloud/spring-cloud-sleuth#1663 opened by @m-grzesiak
It contains the details to understand what is going on, a sample project that reproduces the issue and some investigation details. The issue is very similar to spring-cloud/spring-cloud-sleuth#1660
Description
When an exception is thrown from a method annotated with
@JmsListenerall tracing information is lost when it reaches the error handler and error logs do not contain tracing information.Sample: https://github.com/jonatan-ivanov/sleuth-gh-1663
Investigation details: spring-cloud/spring-cloud-sleuth#1663 (comment) (also see spring-cloud/spring-cloud-sleuth#1660)
Possible fix (breaking change): should be similar to spring-projects/spring-amqp#1287
The text was updated successfully, but these errors were encountered: