[
http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Wringe updated CARGO-706:
------------------------------
Description:
When I do:
$ mvn cargo:deploy
[INFO] [cargo:deploy]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
Error writing request body to server
org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
Caused by: java.io.IOException: Error writing request body to server
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:2637)
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:2620)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109)
at org.codehaus.cargo.container.jetty.JettyRemoteDeployer.pipe(JettyRemoteDeployer.java:309)
With that the upload starts and progresses for awhile, then stops when this error occurs. I believe it actually finishes before the deploy fails.
The Jetty log shows:
2009-06-01 19:11:58.817::WARN: /cargo-jetty-deployer/deploy: java.io.FileNotFoundException: null/webapps/.war (No such file or directory)
Tested with several different versions of the Maven2 cargo plugin including the latest snapshots, and cargo-jetty-deployer 1.0.
Pom fragment:
<configuration>
<type>runtime</type>
<properties>
<cargo.hostname>hostname.com</cargo.hostname>
<cargo.protocol>http</cargo.protocol>
<cargo.servlet.port>8080</cargo.servlet.port>
<cargo.remote.username>maven</cargo.remote.username>
<cargo.remote.password>XXXXX</cargo.remote.password>
</properties>
</configuration>
<deployer>
<type>remote</type>
<deployables>
<deployable>
<groupId>XXXXXXXX</groupId>
<artifactId>XXXXXXXXX</artifactId>
<type>war</type>
<properties>
<context>/</context>
</properties>
</deployable>
</deployables>
</deployer>
See also
http://markmail.org/thread/xlbgyhcuzd7pi62g for another user with a similar problem.
I discussed this issue with mwringe on IRC.
was:
When I do:
$ mvn cargo:deploy
[INFO] [cargo:deploy]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
Error writing request body to server
org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
Caused by: java.io.IOException: Error writing request body to server
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:2637)
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:2620)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109)
at org.codehaus.cargo.container.jetty.JettyRemoteDeployer.pipe(JettyRemoteDeployer.java:309)
With that the upload starts and progresses for awhile, then stops when this error occurs. I believe it actually finishes before the deploy fails.
The Jetty log shows:
2009-06-01 19:11:58.817::WARN: /cargo-jetty-deployer/deploy: java.io.FileNotFoundException: null/webapps/.war (No such file or directory)
Tested with several different versions of the Maven2 cargo plugin including the latest snapshots, and cargo-jetty-deployer 1.0.
Pom fragment:
<configuration>
<type>runtime</type>
<properties>
<cargo.hostname>hostname.com</cargo.hostname>
<cargo.protocol>http</cargo.protocol>
<cargo.servlet.port>8080</cargo.servlet.port>
<cargo.remote.username>maven</cargo.remote.username>
<cargo.remote.password>12345</cargo.remote.password>
</properties>
</configuration>
<deployer>
<type>remote</type>
<deployables>
<deployable>
<groupId>com.powerwood.ross</groupId>
<artifactId>ross-deployable-webapp</artifactId>
<type>war</type>
<properties>
<context>/</context>
</properties>
</deployable>
</deployables>
</deployer>
See also
http://markmail.org/thread/xlbgyhcuzd7pi62g for another user with a similar problem.
I discussed this issue with mwringe on IRC.
> Deploying to jetty via cargo-maven2-plugin and cargo-jetty-deployer fails with IOException
> ------------------------------------------------------------------------------------------
>
> Key: CARGO-706
> URL:
http://jira.codehaus.org/browse/CARGO-706> Project: Cargo
> Issue Type: Bug
> Components: Jetty
> Environment: Jetty 6.1.17
> Reporter: Gabe
>
> When I do:
> $ mvn cargo:deploy
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
> Error writing request body to server
> org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/user/Workspace/deployable/target/deployable-1.0.war]
> Caused by: java.io.IOException: Error writing request body to server
> at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:2637)
> at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:2620)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
> at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109)
> at org.codehaus.cargo.container.jetty.JettyRemoteDeployer.pipe(JettyRemoteDeployer.java:309)
> With that the upload starts and progresses for awhile, then stops when this error occurs. I believe it actually finishes before the deploy fails.
> The Jetty log shows:
> 2009-06-01 19:11:58.817::WARN: /cargo-jetty-deployer/deploy: java.io.FileNotFoundException: null/webapps/.war (No such file or directory)
> Tested with several different versions of the Maven2 cargo plugin including the latest snapshots, and cargo-jetty-deployer 1.0.
> Pom fragment:
> <configuration>
> <type>runtime</type>
> <properties>
> <cargo.hostname>hostname.com</cargo.hostname>
> <cargo.protocol>http</cargo.protocol>
> <cargo.servlet.port>8080</cargo.servlet.port>
> <cargo.remote.username>maven</cargo.remote.username>
> <cargo.remote.password>XXXXX</cargo.remote.password>
> </properties>
> </configuration>
> <deployer>
> <type>remote</type>
> <deployables>
> <deployable>
> <groupId>XXXXXXXX</groupId>
> <artifactId>XXXXXXXXX</artifactId>
> <type>war</type>
> <properties>
> <context>/</context>
> </properties>
> </deployable>
> </deployables>
> </deployer>
> See also
http://markmail.org/thread/xlbgyhcuzd7pi62g for another user with a similar problem.
> I discussed this issue with mwringe on IRC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email