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

Tracing information is missing when Exception is thrown from JmsListener methods #26532

Closed
jonatan-ivanov opened this issue Feb 9, 2021 · 1 comment
Labels
in: messaging Issues in messaging modules (jms, messaging) status: superseded An issue that has been superseded by another

Comments

@jonatan-ivanov
Copy link
Member

jonatan-ivanov commented Feb 9, 2021

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 @JmsListener all 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

@bclozel
Copy link
Member

bclozel commented Sep 28, 2023

This is superseded by #30335

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2023
@bclozel bclozel added status: superseded An issue that has been superseded by another and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging Issues in messaging modules (jms, messaging) status: superseded An issue that has been superseded by another
Projects
None yet
Development

No branches or pull requests

4 participants