JAVA-6369Needs Triage

Command tracing span scope leaks when CommandListener throws

In InternalStreamConnection, the one-way command path (responseExpected=false) dispatches commandSucceeded before closing the tracing scope and ending the span. If a CommandListener throws an Error, tracing cleanup is skipped, leaving the scope active and the span unended and unexported. The same issue behaviour in the asynchronous path. *Acceptance Criteria* * Ensure tracing cleanup executes via try/finally for both sync and async one-way commands.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.