When all the connections in connection-pool become active and another thread tries to fetch new connection and finally not able to get the connection dataSource returns null jdbc connection rather than throwing not able to get the connection.
Simple steps to reproduce.
Set max connection pool size to 0 and min size to 0. And try to get connection. It will return null instead of throwing exception.
Affects: 3.0.6
The text was updated successfully, but these errors were encountered:
I'm afraid there's simply not enough information to work with here. What kind of connection pool? What DataSource implementation? What gives you reason to believe that this behavior is directly or even indirectly related to the Spring Framework?
Feel free to reopen if you believe this issue is indeed a problem with the framework and if you can articulate the steps necessary to reproduce it. Otherwise, please consider posting to [StackOverflow|stackoverflow.com/questions/tagged/spring] or the perhaps the Spring forums.
Shivakumar N opened SPR-10147 and commented
When all the connections in connection-pool become active and another thread tries to fetch new connection and finally not able to get the connection dataSource returns null jdbc connection rather than throwing not able to get the connection.
Simple steps to reproduce.
Set max connection pool size to 0 and min size to 0. And try to get connection. It will return null instead of throwing exception.
Affects: 3.0.6
The text was updated successfully, but these errors were encountered: