When attempting to deploy a large volume of multiple releases processed via an XML input file, the processes appear to hang, then time out, resulting in failed deployments. Multiple occurrences of the following warning and error may then be found in the nolio_dm_all.log file:
[http-nio-8080-exec-180] WARN (SqlExceptionHelper.java:143) - SQL Error: 0, SQLState: null
[http-nio-8080-exec-180] ERROR (SqlExceptionHelper.java:144) - Cannot get a connection, pool error Timeout waiting for idle object
The "Cannot get a connection" timeout error is indicative of a failure connecting to the database. This can be caused by a number of possible events:
- The database is down.
- The network connection between Release Automation and the database is down.
- The database has too large a load (possibly from other systems accessing it concurrently).
If none of the above causes are identified and the issue persists, please open a ticket with Support via https://support.ca.com.