IDM startup: "The datasource configuration of Task Persistence is invalid.: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/idm"
search cancel

IDM startup: "The datasource configuration of Task Persistence is invalid.: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/idm"

book

Article ID: 259723

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Getting the following error during IDM start up

2023-02-10 10:30:00,492 INFO  [ims.Main] (ServerService Thread Pool -- 132) ################################################
2023-02-10 10:30:00,492 INFO  [ims.Main] (ServerService Thread Pool -- 132) ---- CA IAM FW Startup Sequence Initiated. ----
2023-02-10 10:30:00,500 INFO  [ims.Main] (ServerService Thread Pool -- 132) * Startup Step 1 : Attempting to start ServiceLocator.
2023-02-10 10:30:00,691 ERROR [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 132) The datasource configuration of Task Persistence is invalid.: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/idm

Environment

Release :  Identity Manager 14.4

Cause

This is caused by IDM failing to connect to the Task Persistence database.

Resolution

Modified database to use the correct database name and make sure the user has proper database privileges.

You might want to retest External Database connections from vApp as mentioned here - https://knowledge.broadcom.com/external/article?articleId=243483

 

Additional Information

We saw this issue when the database had too many connections from another source than IM.

Check with your DBA which system is using most connections of your database and troubleshoot (restart of this system worked - but this is not long term solution)

Jboss KB:

https://access.redhat.com/solutions/17782

It might also need to tune up the max-pool-size as described:

https://knowledge.broadcom.com/external/article?articleId=240023