使用故障注入验证恢复机制的核心做法是:在单元测试中通过 mock 或测试框架(如 resilience4j、hystrix)模拟下游服务超时、异常或网络中断,并断言系统是否按预期触发重试、熔断或降级逻辑。具体实现时,需配置故障触发条件(如特定错误码或延迟),确保被测组件捕获异常后执行恢复策略,最终验证返回结果是否符合容错设计。

如何模拟下游服务超时以触发重试?
要模拟下游服务超时并验证重试机制,可以使用 Mockito 的 doThrow 或 when-thenThrow 来抛出 TimeoutException,并结合 Resilience4j Retry 模块设置最大重试次数。当调用被 Mock 的服务方法时,前几次调用抛出异常,最后一次返回成功数据,从而触发重试逻辑并验证最终结果。

import io.github.resilience4j.retry.Retry; import io.github.resilience4j.retry.RetryConfig; import org.junit.jupiter.api.Test; import static org.mockito.Mockito.*; import static org.assertj.core.api.Assertions.assertThat; import java.time.Duration; import java.util.concurrent.TimeoutException; public class RetryTest { @Test void testRetryOnTimeout() { // 1. 创建重试配置 RetryConfig config = RetryConfig.custom() .maxAttempts(3) .waitDuration(Duration.ofMillis(10)) .build(); Retry retry = Retry.of("test", config); // 2. 模拟下游服务:前两次超时,第三次成功 DownstreamService mockService = mock(DownstreamService.class); when(mockService.getData()) .thenThrow(new TimeoutException("Simulated timeout")) .thenThrow(new TimeoutException("Simulated timeout")) .thenReturn("Success Data"); // 3. 包装业务逻辑为 Supplier<string> Supplier<string> decoratedSupplier = Retry.decorateSupplier(retry, () -> mockService.getData()); // 4. 执行并验证 String result = decoratedSupplier.get(); assertThat(result).isEqualTo("Success Data"); verify(mockService, times(3)).getData(); } } </string></string>
如何验证熔断器在连续失败后进入开启状态?
验证熔断器机制需要模拟连续失败场景,检查熔断器状态是否从 CLOSED 变为 OPEN,并确认后续调用直接触发降级逻辑而不实际调用下游。使用 Resilience4j CircuitBreaker 时,设置 failureRateThreshold 和 waitDurationInOpenState,通过多次调用抛出异常,然后断言状态变化及降级返回值。
使用 Husky 将 pre-commit、pre-push 和 commit-msg 检查集成到仓库中,以便代理和开发人员在更改离开工作站之前运行相同的本地防护措施。

import io.github.resilience4j.circuitbreaker.CircuitBreaker; import io.github.resilience4j.circuitbreaker.CircuitBreakerConfig; import io.github.resilience4j.circuitbreaker.CircuitBreakerRegistry; import org.junit.jupiter.api.Test; import static org.mockito.Mockito.*; import static org.assertj.core.api.Assertions.assertThat; import java.time.Duration; import java.util.concurrent.Callable; public class CircuitBreakerTest { @Test void testCircuitBreakerOpensOnFailure() { // 1. 配置熔断器:50% 失败率阈值,快速打开 CircuitBreakerConfig config = CircuitBreakerConfig.custom() .failureRateThreshold(50) .waitDurationInOpenState(Duration.ofMillis(10)) .slidingWindowSize(2) .build(); CircuitBreaker circuitBreaker = CircuitBreaker.of("test", config); // 2. 模拟下游服务:始终失败 DownstreamService mockService = mock(DownstreamService.class); when(mockService.getData()).thenThrow(new RuntimeException("Service Unavailable")); // 3. 包装调用 Callable<string> callable = CircuitBreaker.decorateCallable(circuitBreaker, () -> mockService.getData()); // 4. 触发连续失败 try { callable.call(); } catch (Exception e) { /* Expected */ } try { callable.call(); } catch (Exception e) { /* Expected */ } // 5. 验证状态变为 OPEN assertThat(circuitBreaker.getState()).isEqualTo(CircuitBreaker.State.OPEN); // 6. 验证后续调用直接失败(不触发下游) try { callable.call(); fail("Should have thrown CallNotPermittedException"); } catch (io.github.resilience4j.circuitbreaker.CallNotPermittedException ex) { // Success: Circuit is open } verify(mockService, times(2)).getData(); // Only called twice before opening } } </string>
当熔断器处于半开状态时,如何验证部分请求通过?
在熔断器半开(HALF_OPEN)状态下,系统允许少量探测请求通过以测试下游是否恢复。验证此机制需等待 waitDurationInOpenState 时间后,发送一个成功请求,确认熔断器状态转回 CLOSED,且下游服务被调用一次。若探测请求失败,则状态重新回到 OPEN。
import io.github.resilience4j.circuitbreaker.CircuitBreaker; import io.github.resilience4j.circuitbreaker.CircuitBreakerConfig; import org.junit.jupiter.api.Test; import static org.mockito.Mockito.*; import static org.assertj.core.api.Assertions.assertThat; import java.time.Duration; import java.util.concurrent.Callable; public class HalfOpenTest { @Test void testHalfOpenAllowsProbeRequest() throws Exception { CircuitBreakerConfig config = CircuitBreakerConfig.custom() .failureRateThreshold(50) .waitDurationInOpenState(Duration.ofMillis(100)) .slidingWindowSize(2) .build(); CircuitBreaker cb = CircuitBreaker.of("test", config); DownstreamService mockService = mock(DownstreamService.class); // 先触发熔断:两次失败 Callable<string> callable = CircuitBreaker.decorateCallable(cb, () -> mockService.getData()); try { callable.call(); } catch (Exception ignored) {} try { callable.call(); } catch (Exception ignored) {} assertThat(cb.getState()).isEqualTo(CircuitBreaker.State.OPEN); // 等待半开状态 Thread.sleep(150); // 超过 waitDuration // 模拟下游恢复 when(mockService.getData()).thenReturn("Recovered"); // 发送探测请求 String result = callable.call(); assertThat(result).isEqualTo("Recovered"); assertThat(cb.getState()).isEqualTo(CircuitBreaker.State.CLOSED); verify(mockService, times(1)).getData(); // Only one probe call } } </string>
Java免费学习笔记:立即使用
解锁 Java 大师之旅:从入门到精通的终极指南










