Micronaut声明式HTTP客户端连接重置问题求助

问题描述 #

使用Micronaut声明式HTTP客户端调用微服务时，偶尔触发以下错误：

Error occurred reading HTTP response: Connection reset

完整堆栈信息：

{
  "errorMessage":"Error occurred reading HTTP response: Connection reset",
  "stack_trace":[
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"DefaultHttpClient.java","lineNumber":2306,"nativeMethod":false,"className":"io.micronaut.http.client.netty.DefaultHttpClient$11"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":302,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":281,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":273,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"CombinedChannelDuplexHandler.java","lineNumber":424,"nativeMethod":false,"className":"io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"ChannelHandlerAdapter.java","lineNumber":92,"nativeMethod":false,"className":"io.netty.channel.ChannelHandlerAdapter"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"CombinedChannelDuplexHandler.java","lineNumber":145,"nativeMethod":false,"className":"io.netty.channel.CombinedChannelDuplexHandler$1"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"ChannelInboundHandlerAdapter.java","lineNumber":143,"nativeMethod":false,"className":"io.netty.channel.ChannelInboundHandlerAdapter"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"CombinedChannelDuplexHandler.java","lineNumber":231,"nativeMethod":false,"className":"io.netty.channel.CombinedChannelDuplexHandler"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":302,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":281,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":273,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"SslHandler.java","lineNumber":1105,"nativeMethod":false,"className":"io.netty.handler.ssl.SslHandler"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":302,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":281,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":273,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"exceptionCaught","fileName":"DefaultChannelPipeline.java","lineNumber":1377,"nativeMethod":false,"className":"io.netty.channel.DefaultChannelPipeline$HeadContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":302,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"invokeExceptionCaught","fileName":"AbstractChannelHandlerContext.java","lineNumber":281,"nativeMethod":false,"className":"io.netty.channel.AbstractChannelHandlerContext"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"fireExceptionCaught","fileName":"DefaultChannelPipeline.java","lineNumber":907,"nativeMethod":false,"className":"io.netty.channel.DefaultChannelPipeline"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"handleReadException","fileName":"AbstractNioByteChannel.java","lineNumber":125,"nativeMethod":false,"className":"io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"read","fileName":"AbstractNioByteChannel.java","lineNumber":177,"nativeMethod":false,"className":"io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"processSelectedKey","fileName":"NioEventLoop.java","lineNumber":719,"nativeMethod":false,"className":"io.netty.channel.nio.NioEventLoop"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"processSelectedKeysOptimized","fileName":"NioEventLoop.java","lineNumber":655,"nativeMethod":false,"className":"io.netty.channel.nio.NioEventLoop"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"processSelectedKeys","fileName":"NioEventLoop.java","lineNumber":581,"nativeMethod":false,"className":"io.netty.channel.nio.NioEventLoop"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"run","fileName":"NioEventLoop.java","lineNumber":493,"nativeMethod":false,"className":"io.netty.channel.nio.NioEventLoop"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"run","fileName":"SingleThreadEventExecutor.java","lineNumber":986,"nativeMethod":false,"className":"io.netty.util.concurrent.SingleThreadEventExecutor$4"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"run","fileName":"ThreadExecutorMap.java","lineNumber":74,"nativeMethod":false,"className":"io.netty.util.internal.ThreadExecutorMap$2"},
    {"classLoaderName":"app","moduleName":null,"moduleVersion":null,"methodName":"run","fileName":"FastThreadLocalRunnable.java","lineNumber":30,"nativeMethod":false,"className":"io.netty.util.concurrent.FastThreadLocalRunnable"},
    {"classLoaderName":null,"moduleName":"java.base","moduleVersion":"14-ea","methodName":"run","fileName":"Thread.java","lineNumber":832,"nativeMethod":false,"className":"java.lang.Thread"}
  ]
}

原因分析 #

1. 空闲连接被提前关闭：服务器或中间网络设备（防火墙、负载均衡）会对空闲连接设置超时时间，客户端连接池中的连接超过该时间未被使用，再次复用时就会触发Connection reset。堆栈中SSL层抛出异常，说明连接复用阶段SSL握手或数据传输时发现连接已失效。
2. 连接池配置不匹配：Micronaut HTTP客户端默认使用连接池，若连接池的idle-timeout设置大于服务器/中间设备的空闲超时，会出现连接失效未被及时清理的情况。
3. 网络波动：偶尔的网络丢包、延迟会导致SSL连接中断，触发重置。
4. SSL配置不兼容：证书不匹配、SSL协议版本冲突，可能在特定场景下导致连接重置。

修复方案 #

1. 调整连接池超时配置 #

修改Micronaut客户端配置，确保连接池的空闲超时小于服务器/中间设备的超时时间，同时开启连接健康检查：

micronaut:
  http:
    client:
      pool:
        max-idle-time: 30s  # 建议比服务器超时短，比如服务器设60s则设30s
        max-life-time: 5m
        health-check-interval: 10s  # 定期检查连接可用性
        enabled: true

针对声明式客户端，可单独配置：

@Client(value = "target-service", configuration = TargetClientConfig.class)
public interface TargetClient {
    // 接口方法
}

@ConfigurationProperties("micronaut.http.client.target-service")
public class TargetClientConfig extends HttpClientConfiguration {
}

2. 启用重试机制 #

为声明式客户端添加重试逻辑，针对Connection reset这类可重试异常自动重试：

@Client("target-service")
@Retryable(
    attempts = "3",
    delay = "1s",
    multiplier = "2",
    exceptions = {IOException.class, HttpClientResponseException.class}
)
public interface TargetClient {
    @Get("/api/resource")
    HttpResponse<Resource> getResource();
}

也可通过配置文件全局设置：

micronaut:
  retry:
    default:
      attempts: 3
      delay: 1s
      multiplier: 2
    services:
      target-service:
        exceptions:
          - java.io.IOException
          - io.micronaut.http.client.exceptions.HttpClientResponseException

3. 优化SSL配置 #

若问题与SSL握手有关，指定兼容的SSL协议版本并设置握手超时：

micronaut:
  http:
    client:
      ssl:
        enabled: true
        protocol: TLSv1.2,TLSv1.3
        handshake-timeout: 5s

4. 临时禁用长连接（不推荐长期使用） #

如果连接池问题无法快速定位，可临时禁用长连接，每次请求创建新连接（会影响性能，仅作临时排查用）：

micronaut:
  http:
    client:
      keep-alive: false

5. 排查服务器端配置 #

确认目标微服务的连接超时设置（如Tomcat的keepalive_timeout、Nginx的keepalive_timeout），确保客户端max-idle-time小于该值。同时检查服务器是否存在频繁重启、资源耗尽导致主动关闭连接的情况。

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