A client application is trying to connect to the EMS server on the SSL port but using "tcp" protocol rather than "ssl". For example, in the tibemsd.conf file, the following is configured:
listen = ssl://host:7243
But if the client uses URL "tcp://host:7243" to connect to the EMS server then the EMS server will log the above errors.
Issue/Introduction
This article explains what causes the error "SSL handshake failed: ret=-1, reason=unknown protocol" entry in EMS server log.
Resolution
Find out which client application is using the wrong protocol. Note that there will not be any indication in EMS server log which client application caused the problem since the SSL handshake fails. The SSL connection will only be established when the SSL handshake is successful.