[
https://issues.apache.org/jira/browse/IVY-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene updated IVY-1105:
-------------------------------
Fix Version/s: 2.2.0-RC1
(was: trunk)
> 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
> Fix For: 2.2.0-RC1
>
> 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.
