Ant Ivy resolve / Authenticated Proxy Issue

[Susheel Kumar]

Hi,

Sending it to Solr group in addition to Ivy group.


I have been building Solr trunk (
http://svn.apache.org/repos/asf/lucene/dev/trunk/) using "ant eclipse" from
quite some time but this week i am on a job where things are behind the
firewall and a proxy is used.

Issue: When not in company network then build works fine but when inside
company network Ivy stucks during resolve when downloading
https://repo1.maven.org/maven2/org/apache/ant/ant/1.8.2/ant-1.8.2.jar (see
below) I have set ANT_OPTS=-Dhttp.proxyHost=myproxyhost
-Dhttp.proxyPort=8080 -Dhttp.proxyUser=myproxyusername
-Dhttp.proxyPassword=myproxypassword but that doesn't help. Similar
issue i run into with SVN but i was able to specify proxy & auth into
.subversion/servers file and it worked. With Ant Ivy no idea what's
going wrong. I also tried -autoproxy with ant command line but no luck.
In the meantime .ivy2 folder which got populated outside network would help
to proceed temporarily.

Machine : mac 10.10.3
Ant : 1.9.6
Ivy : 2.4.0

Attach build.xml & ivysettings.xml

kumar$ ant eclipse

Buildfile: /Users/kumar/sourcecode/trunk/build.xml

resolve:

resolve:

ivy-availability-check:

ivy-fail:

ivy-configure:

[ivy:configure] :: Apache Ivy 2.4.0 - 20141213170938 ::
http://ant.apache.org/ivy/ ::

[ivy:configure] :: loading settings :: file =
/Users/kumar/sourcecode/trunk/lucene/ivy-settings.xml


resolve:

[Mark Miller]

Have you used jconsole or visualvm to see what it is actually hanging on to
there? Perhaps it is lock files that are not cleaned up or something else?

You might try: find ~/.ivy2 -name "*.lck" -type f -exec rm {} \;

- Mark

Post by Susheel Kumar
Hi,
Sending it to Solr group in addition to Ivy group.
I have been building Solr trunk (
http://svn.apache.org/repos/asf/lucene/dev/trunk/) using "ant eclipse" from
quite some time but this week i am on a job where things are behind the
firewall and a proxy is used.
Issue: When not in company network then build works fine but when inside
company network Ivy stucks during resolve when downloading
https://repo1.maven.org/maven2/org/apache/ant/ant/1.8.2/ant-1.8.2.jar (see
below) I have set ANT_OPTS=-Dhttp.proxyHost=myproxyhost
-Dhttp.proxyPort=8080 -Dhttp.proxyUser=myproxyusername
-Dhttp.proxyPassword=myproxypassword but that doesn't help. Similar
issue i run into with SVN but i was able to specify proxy & auth into
.subversion/servers file and it worked. With Ant Ivy no idea what's
going wrong. I also tried -autoproxy with ant command line but no luck.
In the meantime .ivy2 folder which got populated outside network would help
to proceed temporarily.
Machine : mac 10.10.3
Ant : 1.9.6
Ivy : 2.4.0
Attach build.xml & ivysettings.xml
kumar$ ant eclipse
Buildfile: /Users/kumar/sourcecode/trunk/build.xml
[ivy:configure] :: loading settings :: file =
/Users/kumar/sourcecode/trunk/lucene/ivy-settings.xml

[Shawn Heisey]

Post by Mark Miller
Have you used jconsole or visualvm to see what it is actually hanging on to
there? Perhaps it is lock files that are not cleaned up or something else?
You might try: find ~/.ivy2 -name "*.lck" -type f -exec rm {} \;

If that does turn out to be the problem and deleting lockfiles fixes it,
then you may be running into what I believe is a bug. It is a bug that
was (in theory) fixed in IVY-1388.

https://issues.apache.org/jira/browse/IVY-1388

I have seen the same problem even in version 2.3.0 which contains a fix
for IVY-1388, so I filed a new issue:

https://issues.apache.org/jira/browse/IVY-1489

Thanks,
Shawn

[Susheel Kumar]

Not really. There are no lock files & even after cleaning up lock files (to
be sure) problem still persists. It works outside company network but
inside it stucks. let me try to see if jconsole can show something
meaningful.

Thanks,
Susheel

Post by Shawn Heisey

Post by Mark Miller
Have you used jconsole or visualvm to see what it is actually hanging on

to

Post by Mark Miller
there? Perhaps it is lock files that are not cleaned up or something

else?

Post by Mark Miller
You might try: find ~/.ivy2 -name "*.lck" -type f -exec rm {} \;

If that does turn out to be the problem and deleting lockfiles fixes it,
then you may be running into what I believe is a bug. It is a bug that
was (in theory) fixed in IVY-1388.
https://issues.apache.org/jira/browse/IVY-1388
I have seen the same problem even in version 2.3.0 which contains a fix
https://issues.apache.org/jira/browse/IVY-1489
Thanks,
Shawn

[Mark Miller]

You should be able to easily see where the task is hanging in ivy code.

- Mark

Post by Susheel Kumar
Not really. There are no lock files & even after cleaning up lock files (to
be sure) problem still persists. It works outside company network but
inside it stucks. let me try to see if jconsole can show something
meaningful.
Thanks,
Susheel

Post by Shawn Heisey

Post by Mark Miller
Have you used jconsole or visualvm to see what it is actually hanging

on

Post by Shawn Heisey
to

Post by Mark Miller
there? Perhaps it is lock files that are not cleaned up or something

else?

Post by Mark Miller
You might try: find ~/.ivy2 -name "*.lck" -type f -exec rm {} \;

If that does turn out to be the problem and deleting lockfiles fixes it,
then you may be running into what I believe is a bug. It is a bug that
was (in theory) fixed in IVY-1388.
https://issues.apache.org/jira/browse/IVY-1388
I have seen the same problem even in version 2.3.0 which contains a fix
https://issues.apache.org/jira/browse/IVY-1489
Thanks,
Shawn

[Mark Miller]

I mention the same thing in
https://issues.apache.org/jira/browse/LUCENE-6743

They claim to have addressed this with Java delete on close stuff, but it
still happens even with 2.4.0.

Locally, I now use the nio strategy and never hit it.

- Mark

Post by Shawn Heisey

Post by Mark Miller
Have you used jconsole or visualvm to see what it is actually hanging on

to

Post by Mark Miller
there? Perhaps it is lock files that are not cleaned up or something

else?

Post by Mark Miller
You might try: find ~/.ivy2 -name "*.lck" -type f -exec rm {} \;

If that does turn out to be the problem and deleting lockfiles fixes it,
then you may be running into what I believe is a bug. It is a bug that
was (in theory) fixed in IVY-1388.
https://issues.apache.org/jira/browse/IVY-1388
I have seen the same problem even in version 2.3.0 which contains a fix
https://issues.apache.org/jira/browse/IVY-1489
Thanks,
Shawn
--

- Mark
about.me/markrmiller