Issue with Trace ID and Span ID not Printing in @JmsListener #31720
Labels
for: external-project
Needs a fix in external project
in: messaging
Issues in messaging modules (jms, messaging)
status: invalid
An issue that we don't feel is valid
theme: observability
An issue related to observability and tracing
Affects: 6.1.1
Description:
After upgrading to Spring Boot version 3.2.2, which includes Spring 6.1.1, we've encountered an issue with the @JmsListener annotation. Despite the trace IDs appearing in the W3C propagation type format in the message properties, the @JmsListener is not loading them into the Tracer context. This behaviour was expected to be fixed by a previous ticket (ID: 30335)).
Please note that the issue persists even after upgrading to the latest version.
Steps to Reproduce:
Expected Behavior:
The @JmsListener should automatically load trace IDs into the Tracer context, allowing for proper tracing and logging.
Git Sample:
A sample project which has two examples as jms-tracing-sleuth where tracing is working and another example (jms-no-tracing-micrometer) demonstrating the issue where tracing was broken with micrometer, was used in a previous ticket (ID: 30335). The same project (jms-no-tracing-micrometer) was downloaded and updated to Spring Boot version 3.2.2 for testing.
Reference:
Previous Ticket ID: 30335
Please investigate and address this issue at your earliest convenience. If there are any logs, stack traces, or additional information that would be helpful, please provide them as part of the investigation. Thank you.
The text was updated successfully, but these errors were encountered: