(java.net.SocketException) 处理请求时捕获：对等方重置连接：套接字写入错误答案

【问题标题】：(java.net.SocketException) caught when processing request: Connection reset by peer: socket write error(java.net.SocketException) 处理请求时捕获：对等方重置连接：套接字写入错误
【发布时间】：2015-12-23 02:54:15
【问题描述】：

使用maven插件部署tomcat时遇到I/O exception (java.net.SocketException) caught when processing request: Connection reset by peer: socket write error问题这个问题困扰了我好几天。由于connection reset by peers 错误，我无法使用 tomcat7:deploy 通过 maven 插件上传我的战争文件。这是我的 pom.xml 的一部分

<build>
        <finalName>Project</finalName>
    <pluginManagement>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.3.2</version>
                <configuration>
                    <source>1.7</source>
                    <target>1.7</target>
                </configuration>
            </plugin>
             <plugin>
                <groupId>org.apache.tomcat.maven</groupId>
                <artifactId>tomcat7-maven-plugin</artifactId>
                 <version>2.2</version>
                <configuration>
                    <server>tomcat</server>
                    <url>http://myserver/manager/text</url>
                    <username>admin</username>
                    <password>admin</password>
                    <path>/plainart</path>
                </configuration>
            </plugin>
        </plugins>

    </pluginManagement>

这是控制台日志

[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for cn.edu.xmu.plainart:cn.edu.xmu.plainart:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: cglib:cglib:jar -> version ${cglib.version} vs 2.2.2 @ line 89, column 15
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building cn.edu.xmu.plainart 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] >>> tomcat7-maven-plugin:2.2:deploy (default-cli) > package @ cn.edu.xmu.plainart >>>
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ cn.edu.xmu.plainart ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ cn.edu.xmu.plainart ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ cn.edu.xmu.plainart ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ cn.edu.xmu.plainart ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ cn.edu.xmu.plainart ---
[INFO] 
[INFO] --- maven-war-plugin:2.2:war (default-war) @ cn.edu.xmu.plainart ---
[INFO] Packaging webapp
[INFO] Assembling webapp [cn.edu.xmu.plainart] in [C:\Users\Luna\Documents\GitHub\PiedPiper\Project\target\Project]
[INFO] Processing war project
[INFO] Copying webapp resources [C:\Users\Luna\Documents\GitHub\PiedPiper\Project\src\main\webapp]
[INFO] Webapp assembled in [3376 msecs]
[INFO] Building war: C:\Users\Luna\Documents\GitHub\PiedPiper\Project\target\Project.war
[INFO] WEB-INF\web.xml already added, skipping
[INFO] 
[INFO] <<< tomcat7-maven-plugin:2.2:deploy (default-cli) < package @ cn.edu.xmu.plainart <<<
[INFO] 
[INFO] --- tomcat7-maven-plugin:2.2:deploy (default-cli) @ cn.edu.xmu.plainart ---
[INFO] Deploying war to http://104.236.166.121:8080/plainart  
Uploading: http://104.236.166.121:8080/manager/text/deploy?path=%2Fplainart

[INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset by peer: socket write error
[INFO] Retrying request
Uploading: http://104.236.166.121:8080/manager/text/deploy?path=%2Fplainart

[INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset by peer: socket write error
[INFO] Retrying request
Uploading: http://104.236.166.121:8080/manager/text/deploy?path=%2Fplainart

[INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset by peer: socket write error
[INFO] Retrying request
Uploading: http://104.236.166.121:8080/manager/text/deploy?path=%2Fplainart

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40.818 s
[INFO] Finished at: 2015-12-23T10:51:22+08:00
[INFO] Final Memory: 19M/160M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project cn.edu.xmu.plainart: Cannot invoke Tomcat manager: Connection reset by peer: socket write error -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project cn.edu.xmu.plainart: Cannot invoke Tomcat manager
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke Tomcat manager
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:141)
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:68)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    ... 20 more
Caused by: java.net.SocketException: Connection reset by peer: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
    at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:181)
    at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:115)
    at org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:880)
    at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:89)
    at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
    at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:117)
    at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:265)
    at org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:203)
    at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:236)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:121)
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:742)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:705)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:388)
    at org.apache.tomcat.maven.plugin.tomcat7.deploy.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:85)
    at org.apache.tomcat.maven.plugin.tomcat7.deploy.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:82)
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:132)
    ... 23 more
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

并配置远程tomcat-user.xml。

我不知道如何解决这个问题。如果我可以提供任何对故障排除有用的信息，请告诉我。

提前致谢

【问题讨论】：

你执行的是哪个 mvn 命令？
尝试重新部署，mvn tomcat7:redeploy
我试过了，还是出现了同样的问题。
你的战争规模有多大？还要提供您的 tomcat-users.xml，因为这个问题主要是由于缺少角色引起的。
不是因为tomcat-users.xml，因为我可以用用户名和密码进入tomcat manager gui面板。

标签： java maven sockets tomcat

【解决方案1】：

试试这些，

使用 重新部署 而不是部署
tomcat 中的默认战争大小为 50 MB，如果您的战争大于 50 MB，请尝试增加该值
列出的许多用户导致我在 tomcat-users.xml 中缺少角色。如果缺少，请尝试添加 manager-script 角色，Question Link
Tomcat7 插件可能会从 maven conf settings.xml 而不是 .m2\settings.xml 中选择服务器详细信息。在该文件中添加服务器信息可能会解决问题。

【讨论】：

感谢您的耐心等待！我检查了你所有的列表项目。前3个没问题。但是你提到的maven conf settings.xml在哪里？我之前将服务器详细信息添加到.m2/settings.xml，这可能是主要原因。
$M2_HOME/conf/settings.xml 即在您的 maven 安装目录中。
它变得更好了。但由于同样的问题，停留在2114/16215 KB 。我的war文件大约16M，肯定在限制大小之内。我认为还有其他一些因素可以控制限制。在我之前的尝试中，它停留在“66/16215KB”。
对了，我是通过eclipse安装maven的，所以没有M2_HOME环境变量。我需要尝试手动安装 maven 吗？
如果没有其他工作，您可以尝试外部安装。您始终可以通过 Eclipse 设置 Window -> Preferences -> Maven -> Installations 在嵌入式或外部安装之间切换

【解决方案2】：

除了@Sabir Khan 的回答。需要检查插件配置中server的值是否与settings.xml中的server id一致

所以在pom.xml 你有：

<plugin>
     ...
     <configuration>
          ...
           <server>MyTomcatServer</server>
          ...
     </configuration>
     ...
</plugin>

请确保您拥有 maven 的 settings.xml：

<servers>
    ...
    <server>
        <id>MyTomcatServer</id>
        <username>username_here</username>
        <password>password_here</password>
    </server>
    ...
</servers>

否则tomcat会尝试使用admin账号（如果没有配置，服务器会拒绝auth）

【讨论】：