记录一次Broken Pipe断链问题排查

1. 背景

线上有个后台应用下载时偶发Broken Pipe异常, 堆栈如下:


2022-03-10 18:04:36,075 WARN  [Thread-2754] [c.x.b.p.a.w.c.RedeemController] fail to write excel stream
org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:330) ~[catalina.jar:8.5.59]
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293) ~[catalina.jar:8.5.59]
at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:118) ~[catalina.jar:8.5.59]
at com.xmly.business.promotion.admin.web.utils.RedeemExcelUtils.sendExcelStreamWithPassword(RedeemExcelUtils.java:97) ~[classes/:?]
at com.xmly.business.promotion.admin.web.controller.RedeemController.exportRedeemCodesExcel(RedeemController.java:381) ~[classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_241]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_241]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_241]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_241]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) ~[spring-web-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) ~[spring-web-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:652) ~[servlet-api.jar:?]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) ~[spring-webmvc-5.2.12.RELEASE.jar:5.2.12.RELEASE]
a t javax.servlet.http.HttpServlet.service(HttpServlet.java:733) ~[servlet-api.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.59]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-websocket.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.59]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:28) ~[auth-data-filter-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.UrlFilter.doFilter(UrlFilter.java:136) ~[auth-data-filter-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at org.jasig.cas.client.util.HttpServletRequestWrapperFilter.doFilter(HttpServletRequestWrapperFilter.java:71) ~[java-cas-client-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at org.jasig.cas.client.util.AssertionThreadLocalFilter.doFilter(AssertionThreadLocalFilter.java:50) ~[java-cas-client-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at org.jasig.cas.client.validation.AbstractTicketValidationFilter.doFilter(AbstractTicketValidationFilter.java:289) ~[java-cas-client-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at org.jasig.cas.client.authentication.AuthenticationFilter.doFilter(AuthenticationFilter.java:226) ~[java-cas-client-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleSignOutFilter.java:97) ~[java-cas-client-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.VirtualFilterChain.doFilter(VirtualFilterChain.java:38) ~[auth-data-filter-1.8.6.jar:?]
at com.xmly.ops.auth.data.filter.FilterChainProxy.doFilter(FilterChainProxy.java:77) ~[auth-data-filter-1.8.6.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.59]
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.12.RELEASE.jar:5.2.12.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.59]
at com.xmly.xdcs.spring.filter.XmlyXdcsTraceFilter.doFilter(XmlyXdcsTraceFilter.java:263) ~[xdcs-spring-0.0.20.jar:0.0.20]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) ~[catalina.jar:8.5.59]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:544) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) ~[catalina.jar:8.5.59]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) ~[catalina.jar:8.5.59]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) ~[catalina.jar:8.5.59]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) ~[catalina.jar:8.5.59]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:616) ~[tomcat-coyote.jar:8.5.59]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[tomcat-coyote.jar:8.5.59]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818) ~[tomcat-coyote.jar:8.5.59]
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1620) ~[tomcat-coyote.jar:8.5.59]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-coyote.jar:8.5.59]
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1082) ~[tomcat-coyote.jar:8.5.59]
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:565) ~[tomcat-coyote.jar:8.5.59]
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:543) ~[tomcat-coyote.jar:8.5.59]
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126) ~[?:1.8.0_241]
at sun.nio.ch.Invoker$2.run(Invoker.java:218) ~[?:1.8.0_241]
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112) ~[?:1.8.0_241]
at com.alibaba.ttl.TtlRunnable.run(TtlRunnable.java:59) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_241]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_241]
Caused by: java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[?:1.8.0_241]
at sun.nio.ch.

2. 分析/解决历程

  1. 刚开始我以为是因为数据量大了所以超时, 因为数据本身要调RPC且大于1W数据时会按分表分页查询100次, 而且又是同步下载本身就慢就没管, 写了个手工处理的脚本来处理.
  2. 后来因为工单有点多, 就算用脚本处理也有点烦(打断工作), 累计处理时间可观, 而且还要跟运营解释. 最重要的是老板说没有产出. 于是从这个时候开始, 我打算从根本上一次性解决这个问题. 如果是因为数据量大同步下载导致, 就优化成异步来处理.
  3. 我联系到导出失败最近半年才有, 难道历史数据没有数据量大的吗? 于是我从表发现有大数据量历史数据, 且有成功导出记录, 这时我才发现并不是数据量的问题, 我开始转变方向, 开始排查问题是什么时候开始出现的, 发现和应用上云的时间是耦合的.
  4. 根据报错在网上找到的很多案例发现, 原因可能是: 服务端向Socket写数据时发现, Socket已经关闭了. 再联系到上云时的调用链路是有变化的, 以前是直接h5 -> nginx -> 物理机, (由于上云后应用IP不是固定的)后面变成了h5 -> nginx -> 应用网关 -> Pod节点, 最后联系运维把网关的配置拉出来, 果然超时时间只配置了3s, 调到10s后就好了.

3. 复盘

  1. 根本原因: 连接被关闭,服务端往socket写数据时发现socket已经被关闭了.
  2. 排查思路: 最近做了哪些变更(链路和代码)
  3. 可能原因: 要么操作耗时优化, 要么排查整个链路各节点配置的超时时间

收获:

  1. 发现问题, 优先查看最近有没有变更, 如果影响面很大第一时间回滚
  2. 墨菲定律: 如果有问题, 肯定会出问题
  3. 不要怕暴露/躲避问题, 正视问题/解决问题(不丢人)
  4. 第一时间解决问题, 可以节省很多时间
  • 1
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Broken pipe远程连接错误是指在进行网络通信时,连接的一方突然关闭了连接,而另一方仍然试图发送数据。这种错误通常发生在客户端和服务器之间的通信过程中。 根据引用\[1\]和引用\[2\]中提供的信息,可以了解到解决Broken pipe远程连接错误的方法。首先,需要检查网络连接是否稳定,确保没有网络中断或其他网络问题。其次,可以尝试增加连接超时时间,以便在连接空闲一段时间后自动关闭连接,避免出现Broken pipe错误。此外,还可以尝试优化代码,减少数据传输量,以降低出现Broken pipe错误的可能性。 引用\[3\]中提到了一种可能的原因是服务器端关闭了连接,而客户端仍然试图发送数据。在这种情况下,可以通过在客户端代码中捕获异常并处理它,以避免程序崩溃。可以使用try-catch语句来捕获IOException,并在捕获到异常时进行相应的处理,例如重新建立连接或关闭连接。 总结来说,解决Broken pipe远程连接错误的方法包括确保网络连接稳定,增加连接超时时间,优化代码以减少数据传输量,并在客户端代码中捕获和处理异常。这些方法可以帮助减少Broken pipe错误的发生,并提高网络通信的稳定性和可靠性。 #### 引用[.reference_title] - *1* *2* *3* [排查IOException Broken pipe 错误,偶遇国外小哥](https://blog.csdn.net/u010648555/article/details/122891525)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^insertT0,239^v3^insert_chatgpt"}} ] [.reference_item] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值