Application server has encryption, RDM does not

When the application server has encryption configured but Realtime Dataset Metrics (RDM) does not, an error condition will occur.

The Application server STDOUT will display the following text (this is an example):

App server STDOUT:
[2019-02-11 08:02:57.450 _unp.utils ] - Callservice: Service call failed.
{ Error: connect ECONNRESET 127.0.0.1:48954                              
    at Object.exports._errnoException (util.js:1020:11)                  
    at exports._exceptionWithHostPort (util.js:1043:20)                  
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)      
  code: 'ECONNRESET',                                                    
  errno: 'ECONNRESET',                                                   
  syscall: 'connect',                                                    
  address: '127.0.0.1',                                                  
  port: 48954 }                                                          
Response does not contain set-cookie

The Application server log will record the error, if tracing is enabled. The following is an example entry:

EZD1286I TTLS Error GRPID: 00000008 ENVID: 00000003 CONNID: 000B78BD 
LOCAL: 127.0.0.1..7150 REMOTE: 127.0.0.1..48954 JOBNAME: S3APP12R USERID: S3STC RULE: 
KS3_APPSRV_AS_RDM_CLIENT  RC:  406 Initial Handshake 0000000000000000 000000552EB28F90 
0000000000000000 00000000 RC = 406

This means that an I/O error occurred on the socket. An I/O error occurs if the TCP socket is closed underneath the SSL protocol, such as when a reset is received.

User response

Check the following items:

Ensure that the remote partner is enabled for secure connections.
Determine whether the secure negotiation completed.
Use the AT-TLS Data trace level to determine whether the secure negotiation completed.
Verify that the TCP data is sent by the remote partner. Use a TCP/IP packet trace to verify that the TCP data is sent by the remote partner.