ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

When restart IDM server to do deployment, the deployment failed the first time, and succeed the second time

book

Article ID: 236939

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

When restart IDM server to do deployment, after shut down the server, confirmed the server is shut down and wildfly stops running, then start wildfly, by using ./standalone.sh &

it failed with error as below

2021-11-20 08:44:33,126 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "iam_im.ear")]) - failure description: {
2021-11-20 08:44:33,226 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 15.0.1.Final (WildFly Core 7.0.0.Final) started (with errors) in 19522ms - Started 2848 of 3333 services (166 services failed or missing dependencies, 599 services are lazy, passive or on-demand)

Then shutdown the server again and start wildfly again, the deployment succeed. 

Please see the attached log

IDM server was shut down successfully at 08:42:23, it is restarted at 08:44:14 and deployment failed. Then IDM server was shut down again at 08:47, was restarted at 08:49:39, this time, the deployment succeed. 

IDM server was shut down successfully at 09:24:41, it is restart at 09:28:24 and the deployment failed.

Then IDM server was shut down again at 09:29:30, was restarted at 09:30:08, this time, the deployment succeed. 

Why the deployment always failed at the first time?

Environment

Release : 14.3

Component : IdentityMinder(Identity Manager)

Resolution

This was a unique case.  In this case their network went down improperly which caused stale and hung connections.  This caused the issue with needing to start the IGA suite once, fail, and start it a second time which worked.  Restarted the system did not correct the issue.  

The resolution was to delete the contents of the \temp and \data directory.  There was something cached in those directories causing a dependency to not resolve on first startup.  Once cleared, now IGA suite starts on first try.