IBM Support

Automation Document Processing project deployment fails after five minutes

Troubleshooting


Problem

When you deploy an Automation Document Processing project to runtime, the deployment runs for five minutes then reports that deployment failed.

Symptom

The cpds pod log gives a Read timed out error.
[DBAContentDeployment] [DBAContentDeployment]  UTIL Error:  importCAOntology
java.net.SocketTimeoutException: Read timed out
The spbackend pod log also gives a WORKER_TIMEOUT error.

Cause

Both cpds and backend allow five minutes for an Automation Document Processing project to deploy to an object store.  If the deployment exceeds five minutes, both cpds and backend trigger a timeout.

Resolving The Problem

Increase the timeout from five minutes to ten minutes or another value of your choosing to the cpds jvm timeout and spbackend timeout.
  ecm_configuration:
    document_processing:
      cpds:
        production_setting:
          jvm_customize_options: "DELIM=;-Ddba.content.deployment.socketimeout=600;"


  ca_configuration:
    spbackend:
      timeout: 600

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m3p000000hAKPAA2","label":"Operate-\u003EADP Install\\Upgrade\\Setup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
10 February 2023

UID

ibm16603751

Page Feedback