[siddiqueirshad]

Description

Fixes #8961

JdkHttpSender.send() executes sendInternal(messageWriter) asynchronously via CompletableFuture.supplyAsync(..., executorService).

When an IOException is encountered during transmission:

1. supplyAsync catches the thrown UncheckedIOException(e) and completes the stage exceptionally with a CompletionException.
2. In .whenComplete(...), throwable is a CompletionException wrapping UncheckedIOException wrapping the underlying IOException (such as ConnectException, SocketTimeoutException).
3. Passing CompletionException directly to onError.accept(throwable) causes HttpExporter to record error.type=java.util.concurrent.CompletionException instead of the actual transport failure type, and masks the true cause in FailedExportException.

In contrast, OkHttpHttpSender passes the unwrapped IOException directly from onFailure to onError.

Solution

In JdkHttpSender.whenComplete, unwrap CompletionException and UncheckedIOException to retrieve the underlying exception before passing it to onError.accept(unwrapped).

Updated JdkHttpSenderTest.send_ioException_callsOnError to assert that errorRef.get() is directly an IOException matching the thrown failure.

[linux-foundation-easycla]

• ❌ - login: @siddiqueirshad / name: Mohd Irshad. The commit (30052c0, 716e203) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Closed · refreshed 2026-10-29 21:16 UTC

Status above doesn't look right?

• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[jack-berg]

Duplicate of #8963