讨论区 » AAS-V10企业版 »
v10管控台上选择文件部署到服务器上时候抛出java.io.IOException: Connection is closed
由 peng bo 在 超过 3 年 之前添加
问题:
[2021-11-04T14:01:15] [] [WARNING] [] [javax.enterprise.web] [tid: _ThreadID=56 _ThreadName=ApusicLogManager] [timeMillis: 1636005675500] [levelValue: 900] [[
org.apache.catalina.core.StandardHostValve@2c5d8963: Exception Processing ErrorPage[errorCode=500, location=/500.html]
java.io.IOException: Connection is closed
at org.glassfish.grizzly.nio.NIOConnection.assertOpen(NIOConnection.java:514)
at org.glassfish.grizzly.http.io.OutputBuffer.write(OutputBuffer.java:663)
at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:296)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:283)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:113)
at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:2147)
at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1043)
at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:525)
at org.apache.catalina.servlets.DefaultServlet.doPost(DefaultServlet.java:561)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:665)
...
Caused by: java.io.IOException: 连接被对方重设
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:378)
...
javax.faces.FacesException: No file was uploaded
at com.sun.webui.jsf.renderkit.html.UploadRenderer.encodeEnd(UploadRenderer.java:105)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:595)
at com.sun.webui.jsf.util.RenderingUtilities.renderComponent(RenderingUtilities.java:105)
at com.sun.webui.jsf.renderkit.html.PropertyRenderer.renderPropertyComponents(PropertyRenderer.java:190)
排查过程:
用户在本地浏览器上登入v10管控台,在管控台上部署应用到服务器上。部署过程中出现部署不上的问题。看日志报错可能和网络有关。让客户选择在服务器上部署,可以部署成功。让客户找网络的人去排查
解决方案:
暂时先让客户选择在服务器上部署方式部署。