Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Error when I try deploy application to tomcat7 server

Tags:

I am trying deploy a web application to tomcat7 via eclipse luna, but I am getting this error:

Uploading: http://localhost:8080/manager/text/deploy?path=%2Floja  [INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2Floja  [INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2Floja  [INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2Floja  [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.936 s [INFO] Finished at: 2014-08-15T22:10:04-03:00 [INFO] Final Memory: 13M/112M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project loja: Cannot invoke Tomcat manager: Connection reset -> [Help 1] [ERROR]  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [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 

I also try deploy to tomcat8, but I get this same error.

In my pom.xml, I have this configuration related to this operation:

  <build>     <finalName>loja</finalName>     <plugins>         <plugin>            <groupId>org.apache.tomcat.maven</groupId>            <artifactId>tomcat7-maven-plugin</artifactId>            <version>2.2</version>            <configuration>                 <url>http://localhost:8080/manager/text</url>                 <server>TomcatServer</server>                 <path>/loja</path>                 <username>user001</username>                 <password>123</password>            </configuration>         </plugin>         <plugin>             <groupId>org.apache.maven.plugins</groupId>             <artifactId>maven-war-plugin</artifactId>             <configuration>                 <failOnMissingWebXml>false</failOnMissingWebXml>             </configuration>         </plugin>     </plugins> </build> 

Anyone knows what's happening here?

UPDATE

I try deploy the application with the command mvn:tomcat7 deploy -X and the output was that:

[INFO] Retrying request [DEBUG] Reopening the direct connection. [DEBUG] Connecting to localhost:8080 [DEBUG] Attempt 4 to execute request [DEBUG] Sending request: PUT /manager/text/deploy?path=%2Floja HTTP/1.1 [DEBUG]  >> "PUT /manager/text/deploy?path=%2Floja HTTP/1.1[\r][\n]" [DEBUG]  >> "User-Agent: Apache Tomcat Maven Plugin/2.2[\r][\n]" [DEBUG]  >> "Content-Length: 18783041[\r][\n]" [DEBUG]  >> "Host: localhost:8080[\r][\n]" [DEBUG]  >> "Connection: Keep-Alive[\r][\n]" [DEBUG]  >> "Authorization: Basic dXNlcjAwMToxMjM=[\r][\n]" [DEBUG]  >> "[\r][\n]" [DEBUG] >> PUT /manager/text/deploy?path=%2Floja HTTP/1.1 [DEBUG] >> User-Agent: Apache Tomcat Maven Plugin/2.2 [DEBUG] >> Content-Length: 18783041 [DEBUG] >> Host: localhost:8080 [DEBUG] >> Connection: Keep-Alive [DEBUG] >> Authorization: Basic dXNlcjAwMToxMjM= Uploading: http://localhost:8080/manager/text/deploy?path=%2Floja ... [DEBUG] Connection 0.0.0.0:53183<->127.0.0.1:8080 closed [DEBUG] Closing the connection. [DEBUG] Connection 0.0.0.0:53183<->127.0.0.1:8080 closed [DEBUG] Connection 0.0.0.0:53183<->127.0.0.1:8080 shut down [DEBUG] Connection 0.0.0.0:53183<->127.0.0.1:8080 closed [DEBUG] Connection released: [id: 0][route: {}->http://localhost:8080][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 5] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.271 s [INFO] Finished at: 2014-08-16T08:11:09-03:00 [DEBUG] Connection manager is shutting down [INFO] Final Memory: 14M/109M [INFO] ------------------------------------------------------------------------ [DEBUG] Connection manager shut down 
like image 626
Kleber Mota Avatar asked Aug 16 '14 01:08

Kleber Mota


Video Answer


2 Answers

By default Tomcat has a max upload size of 50MB. (I.e max size of WAR file)

If you require larger file, try increasing max-file-size and max-request-size within the tomcat web.xml. Note: those values are both stored in bytes.

Edit .../webapps/manager/WEB-INF/web.xml. (Ensure the file sizes are larger than the war file your trying to upload). I.e if you require 80MB WAR,

  <max-file-size>82914560</max-file-size>   <max-request-size>82914560</max-request-size> 

Then restart apache tomcat.

https://octopus.com/blog/tomcat-manager-deployment

like image 186
wired00 Avatar answered Oct 04 '22 07:10

wired00


Ok, I had the same issue with tomcat7.

[INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2iplover  [INFO] I/O exception (java.net.SocketException) caught when processing request: Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2iplover  [INFO] I/O exception (java.net.SocketException) caught when processing request:         Connection reset [INFO] Retrying request Uploading: http://localhost:8080/manager/text/deploy?path=%2iplover 

I could not get it to work with

mvn tomcat7:redeploy  

as mentioned here.

My WAR wasn't very large, just 4MB.

Here was the root problem and solution

It is important that your tomcat-users.xml has the correct roles setup. I ONLY had the role manager setup. Adding manager-script seems important and completely solved my problem.

<role rolename="manager"/> <role rolename="manager-script"/> <role rolename="manager-gui"/> <user username="admin" password="admin" roles="manager,manager-gui,manager-script"/> 
like image 41
lawinslow Avatar answered Oct 04 '22 07:10

lawinslow