EMS server reported "Remote end closed the connection" or "Socket error, reason = ****" message after upgrading to EMS 8.3.
Article ID: KB0092840
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
After an EMS server was upgraded to version 8.3, the EMS server log started to log the message, "Remote end closed the connection" or "Socket error, reason = ****" .
Symptoms:
N/A
Cause:
N/A
After an EMS server was upgraded to version 8.3, the EMS server log started to log the message, "Remote end closed the connection" or "Socket error, reason = ****" .
Symptoms:
N/A
Cause:
N/A
Issue/Introduction
EMS server reported "Remote end closed the connection" or "Socket error, reason = ****" message after upgrading to EMS 8.3.
Environment
ALL
Resolution
Since version 8.3, an EMS server will report "Remote end closed the connection" or "Socket error, reason = ****" in the EMS server log (CONNECT trace option is enabled) when a client (usually a non EMS client) tries to create a connection with an EMS server and immediately closes the connection. As an example, run the following command on a Linux machine to connect to an EMS TCP listener port. The "-z" option for the nc command scans for the daemon's listening port without sending any data.
“nc -z <EMS server hostname> <tcp port>”
or
"Socket error, reason = ****"
“nc -z <EMS server hostname> <tcp port>”
The EMS server log will show the following log entry when the "CONNECT" trace option is enabled:
or
"Socket error, reason = ****"
Feedback
Yes
No
Powered by
