IM Startup failed - WFLYDS0022: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

IM startup shows the Wildlfy/JBoss deployment marker files as *.failed instead of *.deployed and the deployment failed and startup log was stuck at 'FIPS mode enabled' line as shown below screenshot.

The iam_im.ear.failed and castylesr5.1.1.ear.failed file show the following error:

 "WFLYDS0022: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment."

Environment

All Identity Manager running on Wildfly or JBoss

Resolution

Modify the IM Wildfly/JBoss standalone xml (exact file will depend on what is being used by your Wildfly/JBoss) to increase the deployment-timeout from 600 to 3600 within the deployment-scanner subsystem to resolve this problem.

  <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="0" deployment-timeout="3600"/>
  </subsystem>

Additional Information

Review the Red Hat Article for further details

WFLYDS0022: Did not receive a response to the deployment operation within the allowed timeout period