Refresh task is getting failed

Hi Team,

The refresh task is failing because of the error shown below. Sailpoint is up and running not face any slowness

sailpoint.tools.GeneralException: Unable to acquire JDBC Connection
at sailpoint.persistence.HibernatePersistenceManager.getObjectByName(HibernatePersistenceManager.java:715)
at sailpoint.persistence.ClassPersistenceManager.getObjectByName(ClassPersistenceManager.java:270)
at sailpoint.server.InternalContext.getObjectByName(InternalContext.java:649)
at sailpoint.server.HeartbeatService$HeartbeatThread.updateHeartbeat(HeartbeatService.java:611)
at sailpoint.server.HeartbeatService$HeartbeatThread.run(HeartbeatService.java:538)
Caused by: sailpoint.tools.GeneralException: Unable to acquire JDBC Connection
at sailpoint.persistence.HibernatePersistenceManager.startTransaction(HibernatePersistenceManager.java:546)
at sailpoint.persistence.HibernatePersistenceManager.getObjectByName(HibernatePersistenceManager.java:708)
… 4 more
Caused by: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:111)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getPhysicalConnection(LogicalConnectionManagedImpl.java:138)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getConnectionForTransactionManagement(LogicalConnectionManagedImpl.java:273)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.begin(LogicalConnectionManagedImpl.java:281)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.begin(JdbcResourceLocalTransactionCoordinatorImpl.java:246)
at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:83)
at org.hibernate.internal.AbstractSharedSessionContract.beginTransaction(AbstractSharedSessionContract.java:471)
at sailpoint.persistence.HibernatePersistenceManager.startTransaction(HibernatePersistenceManager.java:539)
… 5 more
Caused by: java.sql.SQLException: Unable to connect to: jdbc:sqlserver://Test:1433;databaseName=identityiq

@sureshbomm Check if your JDBC is up and running. You can try logging in to IIQ Console to check if IIQ is able to connect to IIQ DB or not.

Iiq console is working fine

Try going to the debug page, then look under Debug → Database. It shows the number of idle/active/maximum connections.

What is the setting that you are using. Let me know.

Is this your local setup or in client env setup?

If you written custom logic for database connection in any of your rule. Then Please check the code from those rules also.

It is my client environment..we added few jars like jconn4-16jar and postgresql then it is failing, we tried to remove those and ran but still not working.is there any way to check quickly?there are so many jdbc apps and rules

@sureshbomm Check if any of your JDBC App is having connection issue. This might cause this problem.

If you have multiple apps and not setup any utility to get the connection status report, then utilize the below report that I have created. I have provided the details in this blog post.

Centralized Application Test Connection Status Reporting - IdentityIQ (IIQ) / IIQ Community Knowledge Base - SailPoint Developer Community

Hi Suresh,

this error sometimes comes from the corrupt workflow cases as well, if you can , can you please delete the workflow cases, and then test it, and see if the error is gone??

Is there any way to find out correptued workflow cases..there are so many .. can’t delete all

since when you started facing the error?? can you delete all those cases for that particular day, since you have put this change?? or day before ..

To find the corrupted objects, check this post.

Correct IDX rule to detect and fix IDX values - Compass

Can you please extend the datasource.maxtotal=350 in iiq properties file