Closed ismaan1998 closed 3 years ago
Hi I have the same issue, any advice?
I checked the stack trace, and it seems that the previous JDBC connection is not getting appropriately closed; that is why there is no pool available during the second run.
Instead of restarting your application, try stopping it and then starting it.
However, this sample service only utilizes the h2 Database which is an in-memory DB, and if replace with some relational database, this problem shouldn't appear
Let me know if this helps.🙂
This issue has been fixed.
Thanks for fixing this. It is working now.
For the very first time it will run.
But after that you'll face the error below -