You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mauritz Lovgren (JIRA)" <ji...@codehaus.org> on 2007/04/27 02:22:26 UTC

[jira] Created: (WAGONFTP-18) Should have option for retry on connection errors during ftp deploy of site

Should have option for retry on connection errors during ftp deploy of site
---------------------------------------------------------------------------

                 Key: WAGONFTP-18
                 URL: http://jira.codehaus.org/browse/WAGONFTP-18
             Project: wagon-ftp
          Issue Type: Improvement
         Environment: OS capable of running Java
            Reporter: Mauritz Lovgren


When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy.
What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer?
E.g. <numReconnectsOnConnectionFailure> or similar that would really help out in these situations.

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

        

[jira] Moved: (WAGON-144) Should have option for retry on connection errors during ftp deploy of site

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGON-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved WAGONFTP-18 to WAGON-144:
--------------------------------------------

    Component/s:     (was: wagon-ftp)
                 wagon-ftp
            Key: WAGON-144  (was: WAGONFTP-18)
        Project: Maven Wagon  (was: wagon-ftp)

> Should have option for retry on connection errors during ftp deploy of site
> ---------------------------------------------------------------------------
>
>                 Key: WAGON-144
>                 URL: http://jira.codehaus.org/browse/WAGON-144
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ftp
>         Environment: OS capable of running Java
>            Reporter: Mauritz Lovgren
>
> When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy.
> What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer?
> E.g. <numReconnectsOnConnectionFailure> or similar that would really help out in these situations.

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

        

[jira] Issue Comment Edited: (WAGONFTP-18) Should have option for retry on connection errors during ftp deploy of site

Posted by "Dmitry Beransky (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/WAGONFTP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112648 ] 

Dmitry Beransky edited comment on WAGONFTP-18 at 11/3/07 1:35 PM:
------------------------------------------------------------------

this problem is not limited to ftp connections.  I'm seeing similar errors deploying a site via webdav.  The issue is that the plugin opens one connection per every file and by doing so oversaturates the system with open connections.  See my post on the maven list here:  http://www.nabble.com/Exception-transfering-site-files-via-webdav-t4734586s177.html


 was:
this problem is not limited to ftp connections.  I'm seeing the same problems with deploying a site via webdav.  The problem is that the plugin opens one connection per every file and by doing so oversaturates the system with open connections.  See my post on the maven list here:  http://www.nabble.com/Exception-transfering-site-files-via-webdav-t4734586s177.html

> Should have option for retry on connection errors during ftp deploy of site
> ---------------------------------------------------------------------------
>
>                 Key: WAGONFTP-18
>                 URL: http://jira.codehaus.org/browse/WAGONFTP-18
>             Project: wagon-ftp
>          Issue Type: Improvement
>         Environment: OS capable of running Java
>            Reporter: Mauritz Lovgren
>
> When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy.
> What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer?
> E.g. <numReconnectsOnConnectionFailure> or similar that would really help out in these situations.

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

        

[jira] Commented: (WAGONFTP-18) Should have option for retry on connection errors during ftp deploy of site

Posted by "Dmitry Beransky (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/WAGONFTP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112648 ] 

Dmitry Beransky commented on WAGONFTP-18:
-----------------------------------------

this problem is not limited to ftp connections.  I'm seeing the same problems with deploying a site via webdav.  The problem is that the plugin opens one connection per every file and by doing so oversaturates the system with open connections.  See my post on the maven list here:  http://www.nabble.com/Exception-transfering-site-files-via-webdav-t4734586s177.html

> Should have option for retry on connection errors during ftp deploy of site
> ---------------------------------------------------------------------------
>
>                 Key: WAGONFTP-18
>                 URL: http://jira.codehaus.org/browse/WAGONFTP-18
>             Project: wagon-ftp
>          Issue Type: Improvement
>         Environment: OS capable of running Java
>            Reporter: Mauritz Lovgren
>
> When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy.
> What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer?
> E.g. <numReconnectsOnConnectionFailure> or similar that would really help out in these situations.

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

        

[jira] Updated: (WAGON-144) Should have option for retry on connection errors during ftp deploy of site

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGON-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated WAGON-144:
-------------------------------

    Fix Version/s: 1.x

> Should have option for retry on connection errors during ftp deploy of site
> ---------------------------------------------------------------------------
>
>                 Key: WAGON-144
>                 URL: http://jira.codehaus.org/browse/WAGON-144
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ftp
>         Environment: OS capable of running Java
>            Reporter: Mauritz Lovgren
>             Fix For: 1.x
>
>
> When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy.
> What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer?
> E.g. <numReconnectsOnConnectionFailure> or similar that would really help out in these situations.

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