[
https://issues.apache.org/jira/browse/MTOMCAT-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227814#comment-13227814
]
William Churchill edited comment on MTOMCAT-116 at 3/12/12 7:46 PM:
--------------------------------------------------------------------
I have a similar problem on a Linux System. I am able to deploy my war file to
a locally running instance of Tomcat (6.0.33). When I try to deploy my war to
a remote system running 6.0.24, I receive the above exception. I can see the
manager console for the remote system to which I am trying to deploy.
The remote system has all requests to port 80 NAT'ed to 8080 where Tomcat is
listening. When I explicitly used port 8080 in my url, it worked. So it
appears port re-directs do not work here. Hope that helps.
was (Author: wchurchill):
I have a similar problem on a Linux System. I am able to deploy my war
file to a locally running instance of Tomcat (6.0.33). When I try to deploy my
war to a remote system running 6.0.24, I receive the above exception. I can
see the manager console for the remote system to which I am trying to deploy.
> NonRepeatableRequestException when executing goal tomcat6:deploy
> ----------------------------------------------------------------
>
> Key: MTOMCAT-116
> URL: https://issues.apache.org/jira/browse/MTOMCAT-116
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
> Affects Versions: 2.0-beta-1
> Environment: Client: Windows 7/Eclipse Indigo/Java 5/m2eclipse
> (embedded mvn 3.0.2/1.0.100.20110804-1717)
> Server: Windows 2003 Server/Tomcat 6.0.32/Java 6/
> Reporter: Michael Yockey
> Assignee: Olivier Lamy
>
> Deployment to Tomcat fails after war upload. The war file does not appear on
> the server but the maven log marks the upload progess to completion. The
> application is not successfully deployed. Here is the relevant stack trace
> from the Maven debugging output:
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy
> (default-cli) on project web-integration: Cannot invoke Tomcat manager
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke
> Tomcat manager
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:152)
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:71)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.http.client.ClientProtocolException
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:926)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
> at
> org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:718)
> at
> org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:681)
> at
> org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:363)
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:87)
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:86)
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:143)
> ... 22 more
> Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry
> request with a non-repeatable request entity.
> at
> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:686)
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923)
> ... 29 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
