ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVY-1327) Hangs when downloading from Jenkins
Date Tue, 03 Jan 2012 08:14:21 GMT

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

Maarten Coene commented on IVY-1327:
------------------------------------

You can disable the HEAD request by adding httpRequestMethod="GET" toyour ivysettings.xml
file:
http://ant.apache.org/ivy/history/latest-milestone/settings/settings.html

Hope this helps...

                
> Hangs when downloading from Jenkins
> -----------------------------------
>
>                 Key: IVY-1327
>                 URL: https://issues.apache.org/jira/browse/IVY-1327
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0
>         Environment: OSX 10.6.8, Ubuntu 10.10
>            Reporter: Larry Edelstein
>
> Ivy fails to download a dependency from Jenkins.
> I've got a Jenkins server on Ubuntu 10.10 and a component build job, and I've got another
project, using Ivy, that depends on that component. That second project's ivysettings.xml
references the Jenkins server as a URL resolver, like http://my.jenkins.server:8080/job/[module]/lastStableBuild/artifact/dist/[module]-[revision].zip.
> What happens when I run Ant locally is that Ivy tries to download the dependency from
Jenkins, but times out. From the log (with -debug):
> [ivy:retrieve] 	 trying http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
> [ivy:retrieve] 		tried http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
> [ivy:retrieve] downloading http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
...
> [ivy:retrieve] 	snaps: downloading http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
> [ivy:retrieve] 		to /Users/larry/.ivy2/cache/klout/perks-security/jars/perks-security-1.1-SNAPSHOT.jar.part
> [ivy:retrieve] HTTP response status: -1 url=http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
> [ivy:retrieve] WARN: 	[FAILED     ] klout#perks-security;1.1-SNAPSHOT!perks-security.jar:
The HTTP response code for http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
did not indicate a success. See log for more detail. (10976ms)
> [ivy:retrieve] WARN: 	[FAILED     ] klout#perks-security;1.1-SNAPSHOT!perks-security.jar:
The HTTP response code for http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
did not indicate a success. See log for more detail. (10976ms)
> [ivy:retrieve] WARN: ==== snaps: tried
> [ivy:retrieve] WARN:   http://perks-srv3:8080/job/perks-security/lastStableBuild/artifact/dist/perks-security-1.1-SNAPSHOT.zip
> [ivy:retrieve] :: resolution report :: resolve 83ms :: artifacts dl 10979ms
> If I fetch that URL with my web browser, or with wget, it downloads just fine. And if
I point Ivy at another webserver with the file, it downloads fine. 
> And there's a Heisenbug aspect to the problem. The dependent project is originally a
Play framework job, which as you may know uses Ivy for dependency resolution. When I ran "play
dependencies" in my debugger, I consistently got success when I set a breakpoint in UrlRepository.get(String,
File), and failure otherwise. Since then I've isolated the problem by creating a test project
without Play and only using Ivy; that's what I've referenced above. I haven't tried debugging
it, but I'd bet I get the same result.
> My hunch is that the problem has something to do with the HEAD request Ivy makes, but
that's just a hunch. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message