Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread 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

Re: Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread 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 On Wed, Sep 16, 2015 at 9:50 AM Susheel Kumar

Re: Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread Shawn Heisey
On 9/16/2015 9:32 AM, Mark Miller wrote: > 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

Re: Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread 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 On Wed, Sep 16, 2015 at 12:17 PM, Shawn Heisey

Re: Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread 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 On Wed, Sep 16, 2015 at 12:17 PM Shawn Heisey

Re: Ant Ivy resolve / Authenticated Proxy Issue

2015-09-16 Thread Mark Miller
You should be able to easily see where the task is hanging in ivy code. - Mark On Wed, Sep 16, 2015 at 1:36 PM Susheel Kumar wrote: > Not really. There are no lock files & even after cleaning up lock files (to > be sure) problem still persists. It works outside company