No open connections were available on endpoint
If a connector is handing a significant amount of eMessage traffic, the logs may contain the following exception:
Connector Exception 22: No open connections were available on endpointAdministrator Actions
Depending on the current setting for the number of connection pipes to the ThingWorx Platform, the administrator can take either of the following actions (or both if after performing the first action, the issue persists):
• Increase the number of connection pipes from the default value of 5 to a higher value (in the configuration file, emessage.conf). Here is the property with the default setting:
transport.websockets {
connections.pipe.count = 5
• If you have increased the number of connection pipes to a large value and the errors persist, install multiple instances of eMessage Connector and use a load balancer to distribute eMessage traffic among them.