ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-1105) Excessive hits to missing URLs uses up all ports on Windows
Date Mon, 27 Jul 2009 22:36:15 GMT

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

Maarten Coene commented on IVY-1105:
------------------------------------

I've committed a potential fix in SVN trunk.
Could you please give it a try to see if it fixes the problem?
I couldn't test it because I'm on windows Vista right now which doens't seem to have the problem
(butI could reproduce the problem earlier this day on a windows XP machine)

> 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
>         Attachments: ApacheURLLister.java
>
>
> 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.


Mime
View raw message