org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
https://blog.csdn.net/u013059432/article/details/80415533
完整錯誤資訊:
org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:396)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:426)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:345)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:298)
at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:151)
at com.wanyu.frame.base.BaseAdminController.outJson(BaseAdminController.java:204)
at com.wanyu.frame.base.BaseAdminController.outResultJson(BaseAdminController.java:305)
at com.wanyu.yuyi.controller.HomeuserController.findList(HomeuserController.java:97)
at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215)
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:749)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:690)
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:83)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:945)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:876)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:961)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:852)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:837)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:94)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:509)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1104)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1524)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1480)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
at sun.nio.ch.IOUtil.write(IOUtil.java:65)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:124)
at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:101)
at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:172)
at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket(InternalNioOutputBuffer.java:140)
at org.apache.coyote.http11.InternalNioOutputBuffer.addToBB(InternalNioOutputBuffer.java:198)
at org.apache.coyote.http11.InternalNioOutputBuffer.access$000(InternalNioOutputBuffer.java:42)
at org.apache.coyote.http11.InternalNioOutputBuffer$SocketOutputBuffer.doWrite(InternalNioOutputBuffer.java:321)
at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:84)
at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:256)
at org.apache.coyote.Response.doWrite(Response.java:491)
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:391)
... 48 more
環境:Eclipse + Tomcat + Spring + Spring MVC + MyBatis
在Eclipse中以Debug模式啟動除錯
錯誤原因:
這個異常是由於以下幾個原因造成。
1、客戶端再發起請求後沒有等伺服器端相應完,點選了stop按鈕,導致伺服器端接收到取消請求(頻繁的重新整理就會產生此問題)。
通常情況下是不會有這麼無聊的使用者,出現這種情況可能是由於使用者提交了請求,伺服器端相應緩慢,比如業務邏輯有問題等原因,導致頁面過了很久也沒有重新整理出來,使用者就有可能取消或重新發起請求。
這種錯誤是合理範圍內的,無法避免的,不必關心它。
2、Tomcat伺服器在接受使用者請求的時候,有其自身的處理能力,執行緒、伺服器等各個資源限制,超出Tomcat承載範圍的請求,就會被tomcat停掉,也可能產生該錯誤。
3、Linux的執行緒機制會產生JVM出錯的問題,特別是在連線高峰期間經常出現這樣的問題,tomcat在linux下也出現類似情況。
提示:
也有可能產生的錯誤是:
java.io.IOException: Connection reset by peer
相關文章
- RedisClient 報出java.net.SocketException: Broken pipe異常RedisclientJavaException
- Kubelet 錯誤日誌 broken pipe 和 connection reset by peer 的原因分析
- oracle ENABLE=BROKENOracle
- [Bash] pipe intro
- [Python] pipe模組Python
- pipe stderr into another process
- java踩坑之java.io.IOException: No space left on deviceJavaExceptiondev
- 精讀《pipe operator for JavaScript》JavaScript
- SGU 124 Broken line(計算幾何)
- Oracle ENABLE=broken引數與TCP KeepAliveOracleTCP
- 對於Pipe管道之愛 - jessfraz
- Pandas - pandas.Series.pipe 函式函式
- Oracle vs PostgreSQL Develop(19) - PIPE ROWOracleSQLdev
- [20200218]ENABLE=BROKEN在連線串中.txt
- OpenCL中的管道cl::Pipe的使用
- linux程式間通訊--管道(PIPE & FIFO)Linux
- HikariDataSource(broken because of SQLSTATE(08S01), ErrorCode(0))SQLError
- java.io.IOException: Could not locate executable null\bin\winutils.exe in the Hadoop(已解決)JavaExceptionNullHadoop
- 小而美的 golang 部落格平臺 PipeGolang
- Python多程式之資料交換PipePython
- [20200218]ENABLE=BROKEN在連線串中4.txt
- 【PAT甲級A1084】Broken Keyboard (20分)(c++)C++
- [20210201]dblink建立連線串使用ENABLE=BROKEN.txt
- JavaScript中的compose函式和pipe函式JavaScript函式
- 「日常訓練」「小專題·USACO」 Broken Necklace(1-2)
- [20200219]strace跟蹤設定ENABLE=BROKEN的情況.txt
- [20200218]無ENABLE=BROKEN在連線串中3.txt
- 2021 OWASP Top 10釋出——Broken Access Control 躍居榜首
- Go 部落格平臺 Pipe 1.8.3 釋出,支援 PJAXGo
- Go 部落格平臺 Pipe 1.6.0 釋出,支援 sitemapGo
- 在pandas中使用pipe()提升程式碼可讀性
- Swoole 原始碼分析——基礎模組之 Pipe 管道原始碼
- Python多程式之Process、Pool、Lock、Queue、Event、Semaphore、PipePython
- [20200220]關於SQLNET.EXPIRE_TIME and ENABLE=BROKEN的總結.txtSQL
- 解讀Node核心模組Stream系列一(Writable和pipe)
- Go 部落格平臺 Pipe 1.8.1 釋出,新主題 FaraGo
- Linux 核心最新高危提權漏洞:髒管道 (Dirty Pipe)Linux
- Go 部落格平臺 Pipe 1.8.2 釋出,支援 GitHub 登入GoGithub