Process in stuck in running stage, not moving past from the first operator
search cancel

Process in stuck in running stage, not moving past from the first operator

book

Article ID: 368935

calendar_today

Updated On:

Products

CA Process Automation Base

Issue/Introduction

Processes in PAM are queuing up and not moving beyond the first operator and causing a backup of processes to collect in the PAM backlog

Environment

Release 4.4 or higher
CA Process Automation

Cause

c2o.log and server.log will both reveal:

c2o.log:
20XX-XX-XX XX:XX:XX,XXX ERROR [com.optinuity.c2o.servicegroup.process.StartProcessServiceOperationRunner] [     Thread-273] Error while reading process outputs from XXXX-XXXX-XXXX-XXXX - reason For input string: "2MB"

server.log:
20XX-XX-XX XX:XX:XX,XXX ERROR [stderr] (XXXX-XXXX-XXXX-XXXX) Exception in thread "XXXX-XXXX-XXXX-XXXX" java.lang.NumberFormatException: For input string: "2MB"

Resolution

Review the OasisConfig.properties file located in X:\Program Files\CA\PAM\wildfly\standalone\.config.  Look for any entries that contain "2MB"  The value should be just "2" (no MB value needed).

Example entry:

oasis.response.payload.size.threshold=2MB

 

Corrected entry:

oasis.response.payload.size.threshold=2

Additional Information

For the above setting, the default value is 4

We strongly recommend it through the UI (configuration tab) and not directly in the OasisConfig file.

Please see also existing documentation that describes the above setting (not visible by default)