Hi everyone,
I'm currently testing the API Server / Web Portal (oneidentity/oneim-api:9.2) deployed in Kubernetes, and I’m encountering a critical issue.
The App Server is deployed and reachable (tested separately).
The API Server has 2 replicas with sticky sessions enabled.
The login page loads fine, and authentication works.
But once logged in, navigating to any section (like Profile, Identity Overview, or Data Administration) leads to long loading times, followed by this error:
"An error occurred while processing your request."
At the same time, I get the following error in the App Server logs:
-------------------
[810153] The database connection was broken.
[System.Data.SqlClient.SqlException] A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 35 - An internal exception was caught)
...
VI.DB.ConnectionBrokenException: The database connection was broken.
This seems to occur during a massive SELECT query on Person, with several joins and a permissions calculation (QER_FTPersonsAreMe_S). The error breaks the execution and causes the UI crash.
--------------------
(I recently tried scaling the deployment to 2 replicas of the API server to check if it helped, but the issue still occurs in the same way.)
Is the error likely caused by connection timeout / pool exhaustion / SQL Server config, or something in the One Identity config?
Would scaling the App Server or increasing SQL timeout help?
Could the query be too heavy for the default SQL Server config (e.g., connection lifetime or max concurrent queries)?
I’m happy to share more details if needed.
Thanks in advance!
Chakir EL HABRIRI