IdentityIQ 8.4 shutting down after 15 minutes

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4p4

Please share any other relevant files that may be required (for example, logs).

Jul 02, 2026 8:35:23 AM com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin
WARNING: ConnectionID:13 ClientConnectionId: e21ab666-d422-47eb-b1a4-aa83c296ec57 Prelogin error: host infstgdbsms180.database.windows.net port 1433 Unexpected end of prelogin response after 0 bytes read
Jul 02, 2026 8:35:23 AM com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin
WARNING: ConnectionID:12 ClientConnectionId: 84397c07-e16b-4916-a60b-145dc86f2384 Prelogin error: host infstgdbsms180.database.windows.net port 1433 Unexpected end of prelogin response after 0 bytes read

Share all details about your problem, including any error messages you may have received.

We recently upgrated IdentityIQ from 8.3 to 8.4, every thing works fine, we can start the service, login and use identityiq. But until 10 to 15 minutes, the CPU is being used at 100% and the service is unavailable. We thought that it was a DB space issue so we purged a lot of elements but that not resolved the issue. The log i pasted earlier are the last thing we see before it shuts down. I know this is not an issue with the db authentication since i managed to login to the console, i don’t know what to do anymore.

2

lower maxActive(and initialSize) in the datasource config to a value under your Azure SQL tier’s max concurrent connections (e.g., 25-30 for lower DTU tiers), restart Tomcat, and monitor sys.dm_exec_connections on the Azure side while it stabilizes.

3

Hello, thanks you for your anwser, i will try this and come back to you soon

4

@CamilleBeaugendre

Doc heck below post as well.

Healthcare Standards: Resolved: Prelogin error with Microsoft SQLServer and JDBC Connections on Named Instances of SQL Server

5

thanks ! i will check that soon

6

@CamilleBeaugendre It looks like connection pool is getting exhausted. The 100% CPU implies that IIQ threads are either stuck in an infinite retry loop or deadlocked waiting for a database connection that will never respond. Please capture threads dumps in your application server:

jcmd <PID> Thread.print > /Path/threaddump.txt

Please check if anything is blocked on db connection.

7

thank you for that answer, i will try this