Article - CS365975

"java.util.concurrent.TimeoutException: Timed out" is seen when viewing or exporting a Document in Integrity Lifecycle Manager configured with Manage Traces

Modified: 24-Mar-2022   


Applies To

  • Windchill PDMLink 11.0 M030 to 11.2
  • ThingWorx Platform 7.1 to 7.4
  • PTC RV&S (formerly Integrity Lifecycle Manager) 11.0 to 11.2

Description

  • Can load Traces as expected in the Item view within Integrity but Document view or Document export fails to load Traces
  • Getting a timeout error with the Integrity Server log set to DEBUG when loading Traces created in Manage Traces
  • Some Traces load correctly correctly and other Traces in the Document view show ERROR
  • Manage Traces is configured and working as expected when viewing Items but shows ERROR on some Traces in the Document view
  • Incoming External Reference (IER) field works for Items but fails for others on a large Document
  • When scrolling a large Document in Integrity some Traces load as expected and some show ERROR
  • Created a Trace within Windchill PDMLink but the Trace's IER field in Integrity shows ERROR in the Document view
  • Traces fail to load in the Documents view within Integrity Lifecycle Manager
    • server.log located in <Integrity Server>\log\ shows the following error:
      • DEBUG [mksis.IntegrityServer] DEBUG java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException: Timed out APIRequestMessage [requestId: 774, endpointId: 68, sessionId: 220322815, method: POST, entityName: PTC.OSLC.IncomingTraceProvider.integritylmpreprod.twxincomingtraceprovider, characteristic: Services, target: GetIncomingTraces]
            at com.thingworx.communications.common.endpoints.CommunicationEndpoint.sendRequest(CommunicationEndpoint.java:522)
            at com.thingworx.communications.common.endpoints.CommunicationEndpoint.sendRequest(CommunicationEndpoint.java:479)
            at com.thingworx.communications.client.BaseClient.sendRequest(BaseClient.java:354)
            ...
    • The following is seen after several Traces have loaded successfully on a Document in Integrity:
      • trace_error.png
    This is a printer-friendly version of Article 365975 and may be out of date. For the latest version click CS365975