Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
On a TOS 6.5.1 fresh install, I'm not able to connect to my compay's proxy to download .jar files or "Additional Packages".
With the exact same configuration (same preferences Network COnnections - same org.eclipse.core.net.prefs file too), it works with TOS 6.5.1M4 studio ...
Any idea ?
A workaround ?
Thanks
Hi,
I have the same problem too
talend version 6.5.1
is it a realse bug ?
Hi,
here's the exception I am getting in studio log file (working with talend TOS vDI 6.5.1)
java.lang.Exception: https://talend-update.talend.com/nexus/service/local/lucene/search?repositoryId=libraries&g=org.talend.libraries&a=tdgssconfig-15.10.00.14,terajdbc4-15.10.00.14&from=0&count=200 at org.talend.core.nexus.HttpClientTransport.doRequest(HttpClientTransport.java:95) at org.talend.core.nexus.NexusServerUtils.downloadDocument(NexusServerUtils.java:193) at org.talend.core.nexus.NexusServerUtils.search(NexusServerUtils.java:146) at org.talend.core.nexus.NexusServerUtils.search(NexusServerUtils.java:131) at org.talend.core.nexus.TalendLibsServerManager.search(TalendLibsServerManager.java:309) at org.talend.librariesmanager.utils.RemoteModulesHelper.searchFromRemoteNexus(RemoteModulesHelper.java:247) at org.talend.librariesmanager.utils.RemoteModulesHelper.access$7(RemoteModulesHelper.java:209) at org.talend.librariesmanager.utils.RemoteModulesHelper$RemoteModulesFetchRunnable.run(RemoteModulesHelper.java:151) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to talend-update.talend.com:443 timed out at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:416) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:643) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784) at org.talend.core.nexus.NexusServerUtils$2.execute(NexusServerUtils.java:181) at org.talend.core.nexus.HttpClientTransport.doRequest(HttpClientTransport.java:88)
When I try to acces the URL pointed in the logs I get Acces Denied
the URL https://talend-update.talend.com/nexus/ is accessible from the browser (test OK) ==> but not from the studio
I noticed a chage in the URL between the two versions 6.3 and 6.51
in 6.3 in the config.in file under configuration folder in the installation path
default.update.site.url=http://update.talend.com/Studio/tos/
HTTP protocol
in 6.5.1 the config.in file under configuration folder in the installation path
default.update.site.url=https://update.talend.com/Studio/tos/
HTTPS protocol
FYI : the same proxy setting is used in talend TOS DI 6.3 and works just fine !
Any Help ?
Thanks
Hello,
Does this issue only repro on talend open studio V 6.5.1?
Best regards
Sabrina
Hi Sabrina,
I am working on talend 6.3.1 and the proxy work fine.
But when I tried 6.5.1 and 6.4.1 (both work with HTTPS URL) I am facing the same problem.
Thanks for your help.
Also experiencing issues with TOS 6.5.1 regarding connecting to the Talend Nexus through a proxy. Worked on 6.4.1 with the same settings as I'm testing 6.5.1 with. Here's an extract of the log:
!ENTRY org.talend.platform.logging 4 0 2018-02-06 12:12:19.661 !MESSAGE 2018-02-06 12:12:18,614 ERROR org.talend.commons.exception.CommonExceptionHandler - Connection to https://talend-update.talend.com refused !STACK 0 org.apache.http.conn.HttpHostConnectException: Connection to https://talend-update.talend.com refused at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190) at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:643) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784) at org.talend.core.nexus.NexusServerUtils$2.execute(NexusServerUtils.java:181) at org.talend.core.nexus.HttpClientTransport.doRequest(HttpClientTransport.java:88) at org.talend.core.nexus.NexusServerUtils.downloadDocument(NexusServerUtils.java:193) at org.talend.core.nexus.NexusServerUtils.search(NexusServerUtils.java:146) at org.talend.core.nexus.NexusServerUtils.search(NexusServerUtils.java:131) at org.talend.core.nexus.TalendLibsServerManager.search(TalendLibsServerManager.java:309) at org.talend.librariesmanager.utils.RemoteModulesHelper.searchFromRemoteNexus(RemoteModulesHelper.java:247) at org.talend.librariesmanager.utils.RemoteModulesHelper.access$7(RemoteModulesHelper.java:209) at org.talend.librariesmanager.utils.RemoteModulesHelper$RemoteModulesFetchRunnable.run(RemoteModulesHelper.java:151) at org.talend.updates.runtime.engine.factory.PluginRequiredMissingJarsExtraUpdatesFactory.retrieveUninstalledExtraFeatures(PluginRequiredMissingJarsExtraUpdatesFactory.java:68) at org.talend.updates.runtime.engine.ExtraFeaturesUpdatesFactory.retrieveUninstalledExtraFeatures(ExtraFeaturesUpdatesFactory.java:49) at org.talend.updates.runtime.ui.CheckExtraFeaturesToInstallJob.run(CheckExtraFeaturesToInstallJob.java:68) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) ... 19 more
Hello,
I found that the default.update.site.url has been changed as https://update.talend.com/Studio/tos/ with HTTPS protocol in talend open studio V 6.3.1.
Could you please create a jira issue of DI project on talend bug tracker? Our developer will check it to see if it is a bug on V 6.5.1
https://jira.talendforge.org/secure/Dashboard.jspa
Best regards
Sabrina
Hi Sabrina,
As requested, I created the JIRA for this issue
https://jira.talendforge.org/browse/TDI-40069
Thanks
Hi,
Except for tSAPConnection(with talend open studio, maybe you are using a custom component), do you get this issue that the studio will not be able to download the jar from the repo on other talend components? We suppose that there should be something wrong with this custom component tSAPConnection(sap-api.jar, ap-impl.jar ).
Thanks for your time.
Best regards
Sabrina
Hi Sabrina,
I have to precise that the proxy problem occurs only with the TOS 6.5.1, not with the TOS 6.4.1 as I said in my previous post.
So, to answer your question, the proxy problem I am facing with TOS 6.5.1 is not related to a particular component.
I have the same isssue even when I try to Install aditionnal packages.
The tSAPConnection I was using is included in studio palette, hence, we are not talking about a custom component !