Wildfly Timeout When Starting ITPAM

Products

CA Process Automation Base

Issue/Introduction

When starting the CA Process Automation Orchestrator service users may see that the service starts, but upon accessing the GUI, the browser may display a 404 error

The following error appears in PAM/logs/server.log:

2026-03-25 10:58:50,812 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@5c6c6e84 for operation add at address [("interface" => "management")] failed -- java.util.concurrent.TimeoutException
2026-03-25 10:58:55,813 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@22ae8ba6 for operation add at address

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [600] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "http-interface")
]'

The following may appear in PAM/wildfly/standalone/log/c2o.log:

2026-03-25 10:59:56,276 ERROR [com.optinuity.c2o.server.ServerController] [ead Pool -- 114] Failed to initialize DDL
java.lang.Exception: Error during initialization

2026-03-25 10:59:56,277 ERROR [com.optinuity.c2o.server.ServerController] [ead Pool -- 114] Server Manager Failed to boot - timeout waiting for database structure adjustment

Environment

PAM 4.4 GA and later

Cause

When the Process Automation service starts, the service will access the ITPAM database and make some adjustments

If a database grows too large, this operation may timeout as the application tries to read the database.

WildFly Default timeout for the deployment is 600 sec which may not be sufficient for the system resources.

Resolution

The root cause of this issue is that the database has grown too large to read in a timely manner.

A temporary solution will be to upgrade the timeout by performing these steps:

1. Look for "urn:jboss:domain:deployment-scanner" in PAM\wildfly\standalone\configuration\standalone-full-ha.xml and modify as follows.

<subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
           <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}" deployment-timeout="1200000"/>
</subsystem>

2. Save Changes

3. Start PAM Services

To truly resolve the issue, we recommend configuring an Archive and Purge policy to keep the database at manageable levels:

Purge Archived Instances

If this error is encountered and the UI is unreachable, then please open a Support Case for assistance with clearing space directly on the database.

Broadcom DOES NOT recommend modifying the database directly without assistance from Broadcom Support.