| Unable to connect to updates repositories [message #771545] |
Tue, 27 December 2011 10:19  |
Shaul Yermol Messages: 2 Registered: December 2011 |
Junior Member |
|
|
Hi all,
I have problems connecting to updates repositories from eclipse (Linux Ubuntu 11.10 64 bit, Eclipse 3.7.1, Java 1.6.0).
Trying to connect to http:/ /download.eclipse.org/releases/indigo gives this log:
Quote:
Unable to read repository at http:/ /download.eclipse.org/releases/indigo/content.xml.
Unable to read repository at http:/ /download.eclipse.org/releases/indigo/content.xml.
Connection reset
Connecting to http:/ /download.eclipse.org/eclipse/updates/3.7, 3.6, etc. gives similar results. (The "space" in links is on purpose, I can't post here links)
But connection to projects repositories like Mylin or ADT works fine.
I tried several solutions, none soleved my problem:
- Switched to official Sun JDK (1.6.0_25)
- Downloaded eclipse instead of using Ubuntu repository
- Defined in ini file "-Djava.net.preferIPv4Stack=true" flag
- deleted cache folder
- Do not use proxy
- It's not a transport/firewall/antivirus problem
From what I see in "wireshark", eclipse tries to retrieve "content.xml" from the update repositories, this file isn't there and it gives up. For some strange reason it does not try to download the right file - compositeContent.jar.
I found a similar bug occurred only on 64 bit systems, but it was almost a year ago and it appears fixed.
Please help!
Eclipse version:
Version: 3.7.1
Build id: M20110909-1335
Java version:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
OS Version:
Ubuntu 11.10 - 64 bit
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Unable to connect to updates repositories [message #1066178 is a reply to message #1066010] |
Mon, 01 July 2013 08:29   |
Paul Montague Messages: 3 Registered: January 2012 |
Junior Member |
|
|
Hi, Cameron,
Yes, the key in my case was checking the port and proxy settings under Window / Preferences / General / Network Connections. I had to correct from a wrong port (25; still don't know how that got entered to begin with) to a usable port (80). Specifically, you need to make sure that whatever outgoing port(s) your organization allows, you're using one of those, and enter the settings for any proxy your organization requires.
Regards,
Paul
Regards,
Paul
[Updated on: Mon, 01 July 2013 08:29] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.02310 seconds