Article - CS284060
How to increase Websocket API request response timeout in ThingWorx
Modified: 21-Jun-2023
Applies To
- ThingWorx Platform 8.0 F000 to 9.5
- Windchill Navigate (formerly ThingWorx Navigate) 1.5.0 to 8.5.0
Description
- When Manage Bindings is selected for ThingWorx remote Properties, timeout errors are shown in the Application Log:
[L: ERROR] [O: c.t.w.BaseService] [I: ] [U: Administrator] [S: ] [T: http-nio-80-exec-150] [context: com.thingworx.webservices.context.HttpExecutionContext@3289c078][message: Timed out APIRequestMessage [requestId: 768, endpointId: -1, sessionId: -1, method: POST, entityName: <Entity_Name>, characteristic: Services, target: GetMetadata]
- Is it possible to increase the API request response time out when trying to bind remote Properties
- Search in Navigate fails with error in Application Log:
ERROR ! : When invoking service,Get, all resource providers failed: {WindchillDemoEpmDocumentResourceProvider=java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Timed out APIRequestMessage [requestId: 44, endpointId: -1, sessionId: -1, method: POST, entityName: <Entity_Name>, characteristic: Services, target: Invoke],
This is a printer-friendly version of Article 284060 and may be out of date. For the latest version click CS284060