2015-09-10 110 views
2

部署Maven項目當我執行MVN tomcat7:部署(和其他東西)我總是得到相同的問題:未能在Tomcat中

[DEBUG] Connection manager shut down 
[ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.1:redeploy (default-cli) on project WebGoat: Invocation de Tomcat manager impossible: Software caused connection abort: socket write error -> 
[Help 1] 
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.1:redeploy (default-cli) on project WebGoat: Invocation de Tomcat manager impossible 
     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:62) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
     at java.lang.reflect.Method.invoke(Method.java:497) 
     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: Invocation de Tomcat manager impossible 
     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: Software caused connection abort: socket write error 
     at java.net.SocketOutputStream.socketWrite0(Native Method) 
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) 
     at java.net.SocketOutputStream.write(SocketOutputStream.java:153) 
     at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) 
     at org.apache.http.impl.conn.LoggingSessionOutputBuffer.write(LoggingSessionOutputBuffer.java:74) 
     at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) 
     at org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:856) 
     at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:98) 
     at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108) 
     at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:122) 
     at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:266) 
     at org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:197) 
     at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:257) 
     at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) 
     at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:708) 
     at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515) 
     at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923) 
     at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822) 
     at org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:721) 
     at org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:684) 
     at org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:367) 
     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:81) 
     at org.apache.tomcat.maven.plugin.tomcat7.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:132) 
     ... 23 more 
[ERROR] 
[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 

的問題是,我不明白問題出在哪裏來自。

我Maven的配置是這樣的:

<server> 
    <id>Catalina</id> 
    <username>admin</username> 
    <password>admin</password> 
</server> 

而且項目的pom.xml包含

<configuration> 
<url>http://localhost:8080/manager/text</url> 
<server>Catalina</server> 
<path>/WebGoat</path> 
<attachArtifactClassifier>exec</attachArtifactClassifier> 
</configuration> 

我已經試過,我對計算器和互聯網找到的所有解決方案。 THX的幫助:)

回答

0
Caused by: java.net.SocketException: Software caused connection abort: socket write error 

這看起來像任何Tomcat沒有運行或者無法正常工作 - 數據實際上是在上傳之前將關閉連接。這裏值得檢查tomcat日誌。
上傳的war是不是太大了,tomcat在上傳過程中關閉了連接?

嘗試增加tomcat上傳大小。開放的webapps /經理/ WEB-INF/web.xml並更改以下部分:

<multipart-config> 
    <max-file-size>60000000</max-file-size> 
    <max-request-size>60000000</max-request-size> 
    <file-size-threshold>0<</file-size-threshold> 
</multipart-config> 
+0

我試過了,它不起作用:(我們錯過了一些東西,當然!!) – pokatore

+0

那麼,無論是檢查tomcat日誌還是使用Linux,您都可以使用: strace -o trace。日誌-s 1024 -f mvn tomcat7:部署 並檢查文件trace.log tomcat是否回答有用的問題,或者它只是直接刪除連接。 –

1

我的朋友解決了這個問題。事實上,server.xml文件中缺少一些東西。我們在連接器配置中添加了maxSwallowSize =「 - 1」。現在一切都好! thx everyone