Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Spring Cloud AWS SQS error handler missing trace context

Open
#11,234 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
aws, java, spring

Research direction

Start with the linked reproduction repository and its Spring Cloud AWS SQS listener and error-handler setup, then trace how context is carried when the listener throws. Done means the ErrorHandler logs contain the same traceId as the listener logs, with the reproduction confirming the behavior.

Written by the indexing model from the issue text.

Description

type: bug report
Tracer Version(s)

1.61.1

Java Version(s)

25

JVM Vendor

Eclipse Adoptium / Temurin

Bug Report

When using Spring Cloud AWS SQS with an error handler, trace context does not propagate from the listener to the error handler.

The current behavior has the TraceId present in the Listener logs and the classes called by it, until an exception is thrown and the trace is lost in the logs of the ErrorHandler.

Expected Behavior

The ErrorHandler logs should contain the same traceId as the listener.

Reproduction Code

The code to reproduce the issue is on the repo:

Dominant language
Java
Stars
737
Forks
361
Avg merge
3d 20h
Merged PRs (30d)
173

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/dd-trace-java

All issues in DataDog/dd-trace-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.