Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <452197722.1248732254891.JavaMail.jira@brutus>
Date: Mon, 27 Jul 2009 15:04:14 -0700 (PDT)
From: "Ernest Pasour (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVY-1105) Excessive hits to missing URLs uses up
 all ports on Windows
In-Reply-To: <639906140.1248722955170.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/IVY-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735801#action_12735801 ] 

Ernest Pasour commented on IVY-1105:
------------------------------------

...but it does not appear that our Ant setup includes any version of http-client.jar.  I'll have to check on that tomorrow.

> Excessive hits to missing URLs uses up all ports on Windows
> -----------------------------------------------------------
>
>                 Key: IVY-1105
>                 URL: https://issues.apache.org/jira/browse/IVY-1105
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0-RC1
>         Environment: windows xp sp3, running Ivy repository through http for remote resolving 
>            Reporter: Ernest Pasour
>            Assignee: Maarten Coene
>
> Modified description to be clearer:
> Ivy is extremely aggressive towards repositories . This can result in  
> failures to resolve, even against a healthy repository and with no network latency. 
> The symptom:
> [ivy:resolve] 01-07-2008 13:16:24
> org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
> [ivy:resolve] INFO: I/O exception (java.net.BindException) caught when
> processing request: Address already in use: connect.
> This is especially a problem with large repositories (lots of revisions) and resolving against latest.integration as this will fetch ivy.xml md5 and sha1 files for every revision.
> As I've included in a comment, the problem appears to be Ivy's attempts to list URLs that don't actually exist.  Ivy builds up URLs using the repository location and appending organizations and module names.  We have ivy chains that contain 5 links or more.  So for each successful attempt to list an URL, there are several attempts to list non-existent URLs.  This is wasteful in terms of time, and can lead to using up all of the available Windows ports on the client machine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.