Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

Sixteen Stars

Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

Hi guys,
I have just had an upgrade from 6.1 to 6.2. Everything was previously working in 6.1. No I cannot connect to the TAC with the 6.2 Studio on Windows 10. A screenshot below shows the issue. I kept my 6.1 Studio install on the machine and weirdly I can see the server with that client, but not the 6.2 client. Everything else is 6.2

This suggests to me that something has changed within the Studio, but I cannot find out what and how I might go about fixing this. I have contacted support, but they are taking a little bit of time to respond. So I thought I would put it out here to see if anyone has seen this and knows how to fix it.
Go. :-)
Community Manager

Re: Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

Hi rhall_2.0
weirdly I can see the server with that client, but not the 6.2 client.

I don't understand what you meant this? Any detailed messages are generated in the log file?
Regards
Shong
----------------------------------------------------------
Talend | Data Agility for Modern Business
Sixteen Stars

Re: Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

I meant that I find it weird that I can connect to the TAC (6.2.1) using the 6.1.1 Studio but not the 6.2.1 Studio on the same machine.
I am getting the following in the log for the 6.2.1 Studio that cannot connect...
!ENTRY org.talend.platform.logging 2 0 2016-09-28 09:19:48.525
!MESSAGE 2016-09-28 09:19:48,525 WARN org.talend.commons.exception.CommonExceptionHandler - Unable to access to url :http://{removed server}:8080/org.talend.administrator
!STACK 0
org.talend.commons.exception.PersistenceException: Unable to access to url :http://{removed server}:8080/org.talend.administrator
at org.talend.repository.remoteprovider.ServletUtil.getContentWithPost(ServletUtil.java:361)
at org.talend.repository.remoteprovider.AdministratorClient.getResponseMessage(AdministratorClient.java:402)
at org.talend.repository.remoteprovider.AdministratorClient.getText(AdministratorClient.java:409)
at org.talend.repository.remoteprovider.AdministratorClient.getJsonObject(AdministratorClient.java:391)
at org.talend.repository.remoteprovider.AdministratorClient.getUpdateRepositoryUrl(AdministratorClient.java:684)
at org.talend.repository.remoteprovider.services.RemoteService.getUpdateRepositoryUrl(RemoteService.java:50)
at org.talend.core.nexus.TalendLibsServerManager.getSoftwareUpdateNexusServer(TalendLibsServerManager.java:317)
at org.talend.core.tis.service.CoreTisService.needUpdate(CoreTisService.java:301)
at org.talend.repository.ui.login.LoginHelper.isStudioNeedUpdate(LoginHelper.java:286)
at org.talend.repository.ui.login.LoginProjectPage$20.run(LoginProjectPage.java:1442)
at org.talend.repository.ui.login.LoginProjectPage$20.run(LoginProjectPage.java:1)
at org.talend.repository.ui.dialog.OverTimePopupDialogTask$1.call(OverTimePopupDialogTask.java:76)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketException: Permission denied: 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.net.NetworkClient.doConnect(NetworkClient.java:175)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
at sun.net.www.http.HttpClient.New(HttpClient.java:308)
at sun.net.www.http.HttpClient.New(HttpClient.java:326)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1283)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1258)
at org.talend.repository.remoteprovider.ServletUtil.getContentWithPost(ServletUtil.java:348)
... 13 more

I've checked network settings and proxy settings, but cannot see any differences between the 6.2.1 Studio and the 6.1.1 Studio. 

Re: Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

I am facing similar issue with Talend 6.2.1. 
Please post the solution if its resolved.
Thanks,
Sridutt
Sixteen Stars

Re: Issue with 6.2 Studio on Windows 10 - Anyone else seen this?

I didn't find a reason for not being able to connect with 6.2.1 while I could connect with 6.1, however I did get this resolved by fixing a problem with the TAC. It turns out that the Tomcat memory settings (that are the default for the install) are not sufficient. This led to TAC grounding to a halt. The way we stopped this was to raise the memory assigned to Tomcat.