WFLYCTL0348: Timeout after [1200] seconds waiting for service container stability
search cancel

WFLYCTL0348: Timeout after [1200] seconds waiting for service container stability

book

Article ID: 194638

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

we  migrated from  wildfly-8.2.1.Final  to wildfly-15.0.1.Final after applying the 14_3-Cumulative-Patches. When starting the IDM it fails with  WFLYCTL0348: Timeout after [1200] seconds waiting for service container stability. I will attach the log to the case. We were scheduled to migrate to 14.3 yesterday 5/19. It is delayed because of this issue.

Environment

Release : 14.3

Component : IdentityMinder(Identity Manager)

Resolution

For this customer they have many IMEs some of these IMEs had public users that were tied to them, but removed form the user stores. This adds to the time it takes to deploy the IME. below you find a way to identify the users tied to IMEs and then check your user directory for these users.

For the public user you have to query the ENVIRONMENT_SETTINGS table with:

USE [imobj]
GO

SELECT *
FROM [dbo].[IM_ENVIRONMENT_JDBC_LD]
Where ATTRIBUTE_NAME = 'user'
GO



This will list your environment OIDs with the Users associated with them.

To tie it together, you will then need to get a list of your OIDS and names:

USE [imobj]
GO


SELECT [UNIQUE_NAME]
,[FRIENDLYNAME]
FROM [imobj].[dbo].[IM_ENVIRONMENT_JDBC]



You would then have to join that data.