CompletableFuture.completedFuture()返回正常完成实例，如何构造已异常完成的实例？

Ah, I get it—you know CompletableFuture.completedFuture() for wrapping a successful result, but you want the opposite: a Future that's already in a failed state, ready to throw an exception when someone tries to retrieve its value. Let's break this down based on your Java version:

Java 9+ (the straightforward approach) #

Java 9 added the CompletableFuture.failedFuture() static method exactly for this scenario. It takes the exception you want the Future to carry and returns a pre-failed CompletableFuture instance right away.

Here's a practical example:

// Create a CompletableFuture already failed with an IOException
CompletableFuture<File> failedFileFuture = CompletableFuture.failedFuture(
    new IOException("Could not read file: missing permissions")
);

// When you attempt to get the result, it propagates the exception
try {
    File result = failedFileFuture.get();
} catch (InterruptedException e) {
    Thread.currentThread().interrupt(); // Properly handle thread interruption
} catch (ExecutionException e) {
    // The original IOException is wrapped in ExecutionException's cause
    System.err.println("Failed to get file: " + e.getCause().getMessage());
}

If you use join() instead of get(), it’ll throw a CompletionException wrapping your original exception—same core behavior, just a more convenient exception type for functional code flows.

Java 8 (compatibility workaround) #

If you’re stuck on Java 8 (which doesn’t have failedFuture()), you can manually initialize a CompletableFuture and immediately mark it as failed using completeExceptionally():

// Start with an incomplete CompletableFuture
CompletableFuture<String> failedFuture = new CompletableFuture<>();
// Mark it as completed with your target exception
failedFuture.completeExceptionally(new IllegalArgumentException("Invalid user ID"));

// Usage example
try {
    String userId = failedFuture.get();
} catch (InterruptedException | ExecutionException e) {
    System.err.println("Error: " + e.getCause().getMessage());
}

A quick heads-up: Once you call completeExceptionally(), the Future is finalized—you can’t re-complete it with a value or another exception. That’s actually where the "CompletableFuture already completed with an exception" error you mentioned comes from, if you try to re-trigger completion later.

Why not just use completedFuture() with an exception? #

To clarify a common pitfall: If you tried CompletableFuture.completedFuture(new RuntimeException(...)), that would create a successfully completed Future whose result is the exception object itself. It won’t throw the exception when you call get()—you’d just get the exception as a return value. That’s not what you want here, which is why we need the dedicated failed completion methods.

内容的提问来源于stack exchange，提问作者Gili