Article - CS235581
DataChange Events Subscribed to isConnected Property Fail With Error in ThingWorx
Modified: 04-Aug-2016
Applies To
- ThingWorx Platform 6.5
Description
- Calling remote services or attempting directly to update remote properties in any DataChange Event Subscriptions on remote things results in the following errors in ScriptLog.log and ApplicationLog.log:
Error processing local event: Execution error in service script [MyRemoteThing isConnected.DataChange] : Wrapped java.util.concurrent.TimeoutException: Timed out APIRequestMessage [requestId: 50, endpointId: -1, sessionId: -1, method: PUT, entityName: MyRemoteThing, characteristic: Properties, target: MyProperty] Cause: Timed out APIRequestMessage [requestId: 50, endpointId: -1, sessionId: -1, method: PUT, entityName: MyRemoteThing, characteristic: Properties, target: MyProperty]
- In addition, the following Warning appears in the ThingWorx logs:
NULL MessageSynchronizationContext! Request either timed-out waiting for this response, or it was received by mistake: ResponseMessage requestId: 50, endpointId: -1, sessionId: -1, code: STATUS_SUCCESS, multipart: false, packet #: 0, total packets: 0
- A subscription to Data Change events on the isConnected property, which calls a remote service, fails to continue after the remote service call.
This is a printer-friendly version of Article 235581 and may be out of date. For the latest version click CS235581