Using SSL, no connection between a fault-tolerant agent and its domain manager

In a network using SSL authentication, no connection can be established between a fault-tolerant agent and its domain manager. The standard lists of the two workstations display messages like in the following examples.
  • On the domain manager, mailman messages: 
    + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ AWSBCV082I Workstation FTAHP, Message: AWSDEB009E Data 
+ transmission is not possible because the connection is broken. 
+ The following gives more details of the error: Error 0.
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ AWSBCV035W Mailman was unable to link to workstation: rsmith297;
+ the messages are written to the PO box.
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  • On the fault-tolerant agent, writer messages: 
    /* *******************************************************************
/* AWSBCW003E Writer cannot connect to the remote mailman. The 
/* following gives more details of the error: "
/* AWSDEB046E An error has occurred during the SSL handshaking. The 
/* following gives more details of the error: error:140890B2:SSL
/* routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned
/* *******************************************************************
/* AWSDEZ003E **ERROR**(cpu secs 0)

Cause and solution:

In the localopts file of either the domain manager or the fault-tolerant agent , the SSL port statement is set to 0.

Correct the problem by setting the SSL port number to the correct value in the localopts file. You then need to stop and restart netman on the workstation so that it can now listen on the correct port number.