Java NoSuchElementException: Timeout Waiting for Idle Object - Troubleshooting Guide - 常规

This exception is thrown when a connection pool is unable to provide an idle object within the specified maximum wait duration.

In this specific case, the exception message indicates that the maximum wait duration is set to 1 minute (PT1M). This means that if a thread requests a connection from the pool and there are no idle connections available, it will wait for a maximum of 1 minute for an idle connection to become available. If no idle connection is available within this time, the exception will be thrown.

To resolve this issue, you can try one or more of the following:

Increase the maximum wait duration: If the current wait duration is too short for your application's needs, you can increase the 'borrowMaxWaitDuration' configuration property to a higher value.
Increase the maximum number of connections in the pool: If the pool does not have enough idle connections to meet the demand, you can increase the 'maxTotal' or 'maxIdle' configuration properties to allow for more connections in the pool.
Optimize the usage of connections: If your application is not releasing connections back to the pool properly, it can lead to a shortage of idle connections. Make sure that you are closing connections after you are done using them, and consider using a connection pool manager that automatically manages connection lifecycle.
Check for any long-running queries or operations: If a query or operation takes an unusually long time to complete, it can tie up a connection and prevent it from being returned to the pool. Make sure that your queries and operations are optimized and do not unnecessarily hold on to connections for extended periods.

By addressing these potential causes, you should be able to resolve the 'Timeout waiting for idle object' exception.