Timeout after [300] seconds when starting Identity Governance on Windows

Products

• CA Identity Governance

Issue/Introduction

The following message occurs during Identity Governance Windows service startup. 

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] 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" => "native-interface") ]'


This can impact both the manual bat file startup, or only impact the Windows service startup.

Environment

Windows 2019, Identity Governance 14.5

Cause

The default deployment timeout for JBoss EAP 7.4.x is set to 300 seconds. If the application server takes more than 300 seconds to start, the deployment fails.

Resolution

The error indicates that the JBoss server encountered a timeout (300 seconds) while setting up the HTTP management interface. JBoss attempted to allocate socket resources from the kernel, but the request was not responded to in a timely manner

Configure in the /bin/ca-gm-run.bat file and then restart Identity Governance:

 -Djboss.as.management.blocking.timeout=600 in %JAVA_OPTS% 


For example:

GM_JAVA_OPTS=$GM_JAVA_OPTS -Djboss.modcluster.proxyList=127.0.0.1:80 -Djboss.as.management.blocking.timeout=600