What Does This Do

Moves the asynchronous RUM servlet fixture from the agent-reserved datadog.trace.* namespace to the application-like test.servlet5 namespace.

The fixture schedules response work through a TimerTask. Generic task instrumentation deliberately excludes agent-owned classes under datadog.trace.*, so the fixture’s task captured a continuation when
scheduled but was not instrumented when executed.

Moving it to an application namespace makes the test exercise the same propagation path as a real servlet application.

flowchart TD
    subgraph Before
        A1[Servlet schedules TimerTask] --> B1[Capture request continuation]
        B1 --> C1[Task class is under datadog.trace.*]
        C1 --> D1[Generic Runnable instrumentation excludes it]
        D1 --> E1[Continuation is never resumed]
    end

    subgraph After
        A2[Servlet schedules TimerTask] --> B2[Capture request continuation]
        B2 --> C2[Task class is under test.servlet5]
        C2 --> D2[Generic Runnable instrumentation applies]
        D2 --> E2[Resume and close continuation]
        E2 --> F2[Complete async response]
    end

Why?

The servlet is a test application fixture, not agent implementation code. Keeping it under the reserved agent namespace made the test unrepresentative and bypassed the instrumentation it was intended to verify.

This change fixes the fixture rather than weakening continuation diagnostics or adding a special case for the test.

Motivation

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]