Identity Governance is unable to start and getting BeanCreationException error in eurekify.log

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Suite

Issue/Introduction

The following exceptions are recorded in Identity Governance (IG) eurekify.log when IG was restarted

Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sageDal' defined in class path resource [META-INF/managerContext.xml]: Cannot resolve reference to bean 'sageDalBase' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sageDalBase' defined in class path resource [META-INF/managerContext.xml]: Cannot create inner bean 'com.eurekify.dal.SageDalImpl#5fd1544f' of type [com.eurekify.dal.SageDalImpl] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.eurekify.dal.SageDalImpl#5fd1544f' defined in class path resource [META-INF/managerContext.xml]: Cannot resolve reference to bean 'txLogService' while setting bean property 'txLogService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'txLogService' defined in class path resource [META-INF/txLog/txLogJmsContext.xml]: Cannot resolve reference to bean 'txLogQ' while setting bean property 'destination'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'txLogQ' defined in class path resource [META-INF/txLog/jboss7JmsContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/txLogQ [Root exception is java.lang.IllegalStateException]

at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:334) [spring-beans-3.2.10.RELEASE.jar:3.2.10.RELEASE]

at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108) [spring-beans-3.2.10.RELEASE.jar:3.2.10.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1418) [spring-beans-3.2.10.RELEASE.jar:3.2.10.RELEASE]

...

at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)

at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)

at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_261]

at org.jboss.threads.JBossThread.run(JBossThread.java:485)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sageDalBase' defined in class path resource [META-INF/managerContext.xml]: Cannot create inner bean 'com.eurekify.dal.SageDalImpl#5fd1544f' of type [com.eurekify.dal.SageDalImpl] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.eurekify.dal.SageDalImpl#5fd1544f' defined in class path resource [META-INF/managerContext.xml]: Cannot resolve reference to bean 'txLogService' while setting bean property 'txLogService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'txLogService' defined in class path resource [META-INF/txLog/txLogJmsContext.xml]: Cannot resolve reference to bean 'txLogQ' while setting bean property 'destination'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'txLogQ' defined in class path resource [META-INF/txLog/jboss7JmsContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/txLogQ [Root exception is java.lang.IllegalStateException]

 

Environment

Release :  Identity Governance 14.4, 14.5

Cause

Corrupted data

Resolution

For the Standalone version:

Remove /tmp and /data directories content under the standalone directory.

For Virtual Appliance version:

If you are experiencing this issue with vApp 14.4.2, please open a case with support and reference patch_vapp HF_VA-14.4.2-20231227101805-DE586953.tgz.gpg 
If you are experiencing this issue with vApp 14.5, please open a case and reference patch_vapp HF_VA-14.5.0-20231227102013-DE586953.tgz.gpg.

You will apply the patch in the tmux session.

The patch will add two new aliases "deleteIDGJMSqueue" and "deleteIDPJMSqueue" to delete the JMS temp files from Identity Governance and Identity Portal respectively.
After applying the patch, you must relogin as 'config' user and the new aliases will appear.

You do not need to reboot the vApp machine just to run the "deleteIDGJMSqueue" or "deleteIDPJMSqueue" aliases to delete the JMS temp files. However, the patch does change some OS related configurations too. You can reboot the vApp machine during scheduled down time to reflect the configurations.