Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Jakarta-RS scope remains active after Tomcat request completes (TomEE/CXF), eventually exceeding scope depth

オープン
  • 何か問題がありますか？
#12,597 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
java
領域
observability-sre

調査の方向性

Start with JakartaRsAnnotationsInstrumentation.java at the linked advice, then compare the Tomcat instrumentation and scope-manager sources against the v1.65.1 tag. Investigate which advice-exit path could leave the Jakarta-RS scope active after the servlet request, using the reported scope-depth and out-of-order-close symptoms; completion requires a reproducible diagnosis and confirmation that each request restores the worker scope depth.

索引モデルが issue の本文から書いたものです。

説明

type: bug report
Tracer Version(s)

Datadog dd-trace-java v1.65.1 (official source compared). The debug capture is from a downstream-derived build; the official binary has not been independently run in this environment.

Java Version(s)

Java 17.0.9 / IBM OpenJ9 0.41.0

JVM Vendor

IBM SDK / Semeru

Bug Report
Context and upstream comparison

TomEE/Tomcat with CXF Jakarta-RS. I compared the affected build with the official Datadog v1.65.1 tag. The Jakarta-RS annotations instrumentation source tree, Tomcat instrumentation source tree, scope-manager source tree, ExtractedSpan.java, and LogbackLoggerInstrumentation.java are byte-for-byte identical. In particular, the Jakarta-RS advice in v1.65.1 has the same scope lifecycle code.

One downstream Logback event instrumentation file differs, so I am not claiming that the exact log output or missing correlation IDs have been reproduced with the official Datadog artifact. This report focuses on the scope-stack symptom. Source equivalence also does not, by itself, prove that the official binary exhibits the same runtime behavior.

Observed sequence in a sanitized tracer debug capture
  1. A Jakarta-RS span starts for an annotated resource method on a Tomcat worker.
  2. When the outer servlet request completes, closing its scope logs "scope when not on top" and identifies the still-active Jakarta-RS span as the current top. The example Jakarta-RS span has no matching finish record in the available capture.
  3. Similar out-of-order closes recur on worker threads. Later, activation of new request spans reports "Scope depth limit exceeded (100). Returning NoopScope."

Please investigate whether the Jakarta-RS advice can leave a resource-method scope active after the Tomcat request finishes in a TomEE/CXF deployment, and whether this behavior is already addressed upstream. The capture does not identify which specific advice-exit path was missed.

A related Logback null TraceConfig path is already addressed by #12413; that is not the requested fix here.

Expected Behavior

The Jakarta-RS scope closes before the outer servlet request scope, and each completed request leaves the worker scope stack at its original depth.

Reproduction Code

No standalone reproducer against the official Datadog binary is available yet. No customer logs or internal URLs are attached.

主要言語
Java
スター
736
フォーク
364
平均マージ
3日 13時間
マージ済み PR（30日）
213

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DataDog/dd-trace-java のほかの issue

DataDog/dd-trace-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。