Connector Exception 10: ThingWorx Platform not responding to SDK requests
This Connector exception appears if eMessage Connector does not receive responses to requests from the ThingWorx Platform in the number of seconds configured for the request timeout (10 seconds by default), and an agent is sending data item messages to the Connector. For more information, refer to Observation 14: ThingWorx Platform stops responding to connector SDK (websocket) requests.
Here is a scenario that would result in this exception being logged at the Connector:
1. The ThingWorx Platform is running with remote debugging enabled.
2. The eMessage Connector is started.
3. ThingWorx Platform does not respond to requests from the Connector.
4. An Axeda agent sends data item messages to the Connector.
* 
The ThingWorx Platform may or may not process the requests, but once a request times out, the Connector logs messages similar to those listed below. For information about the property that sets the request timeout (request.default_timeout-ms), refer to Configuring Additional Properties for the Connection.
In this scenario, the Connector sends requests to the ThingWorx Platform and the requests time out after 10 seconds. The message that is logged includes the timeouts:
... ERROR c.t.p.e.converters.EgressConverter -
Error occurred while dequeuing egress for ThingName=Weather1,
error=Timed out waiting for response
...ERROR c.t.p.e.EmessageRequestContext -
converter=DataConverter contextId=73: failure occurred:
failureMessage=Error writing properties during Data Item conversion
java.util.concurrent.TimeoutException: Timed out waiting for response
...
Error occurred while dequeuing egress for ThingName=Weather1,
error=Timed out waiting for response
...ERROR c.t.p.e.EmessageRequestContext -
converter=DataConverter contextId=74: failure occurred:
failureMessage=Error writing properties during Data Item conversion
java.util.concurrent.TimeoutException: Timed out waiting for response
...
Was this helpful?