[jira] Created: (CARGO-706) Deploying to jetty via cargo-maven2-plugin and cargo-jetty-deployer fails with IOException

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>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.

--
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

     [ 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

    [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179239#action_179239 ]

Matt Wringe commented on CARGO-706:
-----------------------------------

The issue has been fixed in svn and will appear shorly in a new 1.0.1-SNAPSHOT.
Can you please try this snapshot and see if it fixes your problem.

> 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

    [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179696#action_179696 ]

Gabe commented on CARGO-706:
----------------------------

Updated the plugin to latest snapshot. No change; exactly the same error.

Request log:

10.43.51.128 - maven [08/Jun/2009:18:58:52 +0000] "PUT /cargo-jetty-deployer/deploy?path=/ HTTP/1.1" 500 0

Stderr:

2009-06-08 11:58:52.720::WARN:  /cargo-jetty-deployer/deploy: java.io.FileNotFoundException: null/webapps/.war (No such file or directory)

I am trying to deploy the application as "ROOT.war" ( "/" context) on the server. This means that cargo-jetty-deployer needs to save the .war file as ROOT.WAR when it's told to deploy the webapp to /. That seems to be one problem.

When I set the <context> to /test123 instead of /, I get the following on the server:

/cargo-jetty-deployer/deploy: java.io.FileNotFoundException: null/webapps/test123.war (No such file or directory)

So it looks like a couple of problems on the deployer side to me - deployer's not grabbing the webapp folder from the environment, and not inferring the 'ROOT.war' file name when deploying to /.

(Visible to LoggedIn role)

> 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

    [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179697#action_179697 ]

Matt Wringe commented on CARGO-706:
-----------------------------------

it looks like you are not using the latest snapshot of the jetty deployer (thats where the fixes were done).

The root.war issue is something that should be looked into.

> 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

    [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179721#action_179721 ]

Gabe commented on CARGO-706:
----------------------------

Hmm, you're right. My bad.

With the latest deployer snapshot, I am able to deploy as expected to any context except "/".

However, deploying to "/ROOT" works fine.

Thanks for your help with this, Matt.
(Visible to LoggedIn role)

> 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

    [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179722#action_179722 ]

Gabe commented on CARGO-706:
----------------------------

Actually, spoke too soon - deploying to /ROOT correctly names the war "ROOT.war", but incorrectly installs it at /ROOT. Close!
(Visible to LoggedIn role)

> 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

     [ http://jira.codehaus.org/browse/CARGO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabe updated CARGO-706:
-----------------------

    Attachment: jetty-deployer_r1956.patch

Patch to fix deployment to the root web application context.

> 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
>         Attachments: jetty-deployer_r1956.patch
>
>
> 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