You may not be able to connect to the TDV server via TDV Studio 8.5.x, which results in the following error:
=======
Unable to connect to the server.
Cause: Failed to connect to https://test.demo.net:9402/cdms/webapi; nested exception is: 
    java.rmi.RemoteException: HTTP transport error: java.net.SocketException: Unexpected end of file from server; nested exception is: 
    HTTP transport error: java.net.SocketException: Unexpected end of file from server

An internal error has occurred.
Cause: Failed to connect to https://test.demo.net:9402/cdms/webapi; nested exception is: 
    java.rmi.RemoteException: HTTP transport error: java.net.SocketException: Unexpected end of file from server; nested exception is: 
    HTTP transport error: java.net.SocketException: Unexpected end of file from server [Log ID: 47d7d6c1-3ef7-4597-9faa-9bb80273c894] 
Version Information: Studio 8.5.1.001
=======

This article explains how to resolve SSL related error 'java.net.SocketException: Unexpected end of file from server; nested exception is: HTTP transport error: java.net.SocketException: Unexpected end of file from server', while using TIBCO Data Virtualization studio 8.5.x

Windows/ Linux

To resolve this error, you need to make sure that you have the below configuration in TDV Studio set to FALSE.
Note: TDV server restart is needed after this change.

TDV Studio -> Administration -> Configuration -> Server -> Communications -> Enable Client Authentication

If this value is set to TRUE, then TDV requires the client to send a client certificate to TDV as part of mutual authentication. 
Note: This setting is by default set to TRUE in 8.5.x and didn’t exist in 8.4. 

Also, we can change this configuration by adding the below attributes to the server_value.xml file.
--------------------------------
<common:attribute>
 <common:name>/server/communications/wantClientAuthenticationOnServerRestart</common:name>
    <common:type>BOOLEAN</common:type>
    <common:value>false</common:value>
  </common:attribute>
--------------------------------

Note: A server restart is required after making these changes to the server_value.xml file. Also, paste the above lines under the server/communication tree (referring to the attached screenshot):