Re: [jbosstools-dev] AERI exception: Can't connect to SOCKS proxy

During the whole evening, while working with jbt-openshift i got the following excpeption, which can be seen as a warning in Eclipse Error Log view: !ENTRY org.eclipse.epp.logging.aeri.ide 2 16 2016-09-02 01:37:53.771 !MESSAGE Server ‘org.eclipse.epp.logging.aeri.ide.server’ failed with exception: Can't connect to SOCKS proxy:connect timed out. ; version: 2.0.1.v20160605-1811 !STACK 0 java.net.SocketException: Can't connect to SOCKS proxy:connect timed out at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428) at java.net.Socket.connect(Socket.java:589) at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72) at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:371) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at org.apache.http.client.fluent.Executor.execute(Executor.java:206) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:205) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:68) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:101) at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54) at com.google.common.util.concurrent.Callables$3.run(Callables.java:93) at java.lang.Thread.run(Thread.java:745) Does anybody else got this? Is it a temporary unavailability problem? Or is it a problem on my laptop? Best regards, Dmitrii _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev