We recently upgraded to SailPoint IdentityIQ 8.5 and are seeing a recurring critical database connection issue.
Every 2–3 weeks, during the Identity Refresh task, the system exhausts all database connections and throws:
Unable to acquire JDBC connection
This happens specifically when both Process Events and Synchronize Attributes are enabled.
We have already adjusted the JDBC connection pool, idle timeout, and connection timeout settings based on SailPoint recommendations, but the issue still returns.
A hard restart of the application servers temporarily clears the problem, but the connection pool slowly degrades again over time.
Since this started immediately after the 8.5 upgrade, we suspect a possible connection leak, unclosed Hibernate session, or framework issue triggered by lifecycle events or attribute synchronization.
Has anyone seen this issue in IIQ 8.5?
Are there any known defects, hotfixes, recommended logging categories, or troubleshooting steps to identify whether the leak is coming from workflows, rules, lifecycle events, or IdentityIQ framework code?
Hi Jagan,
1.Capture thread dumps when the pool is exhausted to see which threads are waiting on JDBC connections.
2.Enable targeted DEBUG/TRACE logging around Identity Refresh, Workflower, LCM, Provisioning, and Hibernate/DB connection handling.
3. It may also be worth checking the database indexes, as rebuilding fragmented indexes resolved a similar issue in one of our projects.
Max Concurrent Session allowed in iiq.properties vs at your Database end. You can consider increasing the number of sessions.
Check if there are threads which are executing heavy query that increase the tempdb and eventually forcing dB to reject the requests and you’ll also see degradation.