Bug 517205 - Connection to eclipse/updates/4.7/p2.index failed on SOCKS : authentication failed
Summary: Connection to eclipse/updates/4.7/p2.index failed on SOCKS : authentication f...
Status: NEW
Alias: None
Product: ECF
Classification: RT
Component: ecf.filetransfer (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-24 09:28 EDT by Yousha Aleayoub CLA
Modified: 2017-05-26 12:07 EDT (History)
1 user (show)

See Also:


Attachments
ECF version (17.81 KB, image/png)
2017-05-25 07:46 EDT, Yousha Aleayoub CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousha Aleayoub CLA 2017-05-24 09:28:56 EDT
What steps will reproduce the problem?
1. Just tried to install a plugin(ADT) and got this error on "checking dependencies".
2. 
3. 


-- Error Details --
Date: Wed May 24 17:46:00 IRDT 2017
Message: Connection to http://download.eclipse.org/eclipse/updates/4.7/p2.index failed on SOCKS : authentication failed. Retry attempt 0 started
Severity: Warning
Product: Eclipse 4.7.0.20170201-1657 (org.eclipse.epp.package.java.product)
Plugin: org.eclipse.equinox.p2.transport.ecf
Session Data:
eclipse.buildId=4.7.0.I20170126-1030
java.version=1.8.0_102
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

Exception Stack Trace:
java.net.SocketException: SOCKS : authentication failed
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:473)
	at java.net.Socket.connect(Socket.java:589)
	at org.eclipse.ecf.internal.provider.filetransfer.httpclient4.ECFHttpClientProtocolSocketFactory.connectSocket(ECFHttpClientProtocolSocketFactory.java:86)
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1084)
	at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:1075)
	at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:1071)
	at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Comment 1 Yousha Aleayoub CLA 2017-05-25 07:46:04 EDT
Created attachment 268564 [details]
ECF version

My Eclipse's ECF version
Comment 2 Scott Lewis CLA 2017-05-25 12:42:15 EDT
Hi Yousha,

From the stack trace, this appears to be caused by some missing or incorrect data in the proxy configuration relative to your networking environment.

In Eclipse, would you please try to go to menu Window->Preferences, select General->Network Connections and be sure that the appropriate SOCKS proxy information and username/password information is entered there.  

There is more information on this help page about the proxy UI/Dialog:

https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-preferences.htmhttps://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-preferences.htm
Comment 3 Yousha Aleayoub CLA 2017-05-25 18:42:18 EDT
(In reply to Scott Lewis from comment #2)
> Hi Yousha,
> 
> From the stack trace, this appears to be caused by some missing or incorrect
> data in the proxy configuration relative to your networking environment.
> 
> In Eclipse, would you please try to go to menu Window->Preferences, select
> General->Network Connections and be sure that the appropriate SOCKS proxy
> information and username/password information is entered there.  
> 
> There is more information on this help page about the proxy UI/Dialog:
> 
> https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.
> user%2Freference%2Fref-net-preferences.htmhttps://help.eclipse.org/neon/
> index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-
> preferences.htm


Hi

I don't use any proxy... 
Active provider: Native
Proxy entries: all UNCHECKED
Proxy bypass: all UNCHECKED
Comment 4 Scott Lewis CLA 2017-05-25 19:46:40 EDT
(In reply to Yousha Aleayoub from comment #3)
> (In reply to Scott Lewis from comment #2)
> > Hi Yousha,
> > 
> > From the stack trace, this appears to be caused by some missing or incorrect
> > data in the proxy configuration relative to your networking environment.
> > 
> > In Eclipse, would you please try to go to menu Window->Preferences, select
> > General->Network Connections and be sure that the appropriate SOCKS proxy
> > information and username/password information is entered there.  
> > 
> > There is more information on this help page about the proxy UI/Dialog:
> > 
> > https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.
> > user%2Freference%2Fref-net-preferences.htmhttps://help.eclipse.org/neon/
> > index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-
> > preferences.htm
> 
> 
> Hi
> 
> I don't use any proxy... 
> Active provider: Native
> Proxy entries: all UNCHECKED
> Proxy bypass: all UNCHECKED

That's very strange.

Your stack trace indicates that a java.net.SocksSocketImpl.connect fails here:

Exception Stack Trace:
java.net.SocketException: SOCKS : authentication failed
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:473)
	at java.net.Socket.connect(Socket.java:589)
	at o

Prior to the connect, ECF creates a socket using a Httpclient Scheme and a SocketFactory and these end up creating the SocksSocketImpl based upon the proxy setting from java properties and from Eclipse proxy settings.

I don't currently understand why you are creating/getting a SocksSocketImpl in your environment with no proxy settings in Eclipse, and presumably no proxy actually present in your network environment.

Since this is on windows could you please check via Internet Explorer->Internet Options->Connections->LAN Settings and report if the Proxy server is checked, and if so what information if any presented via the Advanced button.  thanks.
Comment 5 Yousha Aleayoub CLA 2017-05-26 04:14:23 EDT
(In reply to Scott Lewis from comment #4)
> That's very strange.
> 
> Your stack trace indicates that a java.net.SocksSocketImpl.connect fails
> here:
> 
> Exception Stack Trace:
> java.net.SocketException: SOCKS : authentication failed
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:473)
> 	at java.net.Socket.connect(Socket.java:589)
> 	at o
> 
> Prior to the connect, ECF creates a socket using a Httpclient Scheme and a
> SocketFactory and these end up creating the SocksSocketImpl based upon the
> proxy setting from java properties and from Eclipse proxy settings.
> 
> I don't currently understand why you are creating/getting a SocksSocketImpl
> in your environment with no proxy settings in Eclipse, and presumably no
> proxy actually present in your network environment.
> 
> Since this is on windows could you please check via Internet
> Explorer->Internet Options->Connections->LAN Settings and report if the
> Proxy server is checked, and if so what information if any presented via the
> Advanced button.  thanks.

All UNCHECKED and address, port are empty/disable
Comment 6 Scott Lewis CLA 2017-05-26 12:07:56 EDT
(In reply to Yousha Aleayoub from comment #5)

> 
> All UNCHECKED and address, port are empty/disable

Ok.  I'm currently at a loss to explain this or even reproduce it.  

I see that your version of 4.7 was a while ago:

Product: Eclipse 4.7.0.20170201-1657 (org.eclipse.epp.package.java.product)

Could you please try to reproduce it in your environment by installing a more recent version of 4.7/Oxygen?...e.g. rc2:

http://download.eclipse.org/eclipse/downloads/drops4/S-4.7RC2-201705242000/

There were some issues with httpclient versions in previous versions of Oxygen, so I'm thinking that perhaps that has something to do with what you are experiencing.