SBarnes wrote:We have a client who is running the api against Azure SQL and the api sometimes drops its connection to the database, a service restart fixes the issue and I have already increased the timeout, Jiwa itself goes on quite happily from the same Azure vm which I suspect is due to its baked in redundancy to reconnect itself, in having a quick look at ORMLite under the hood it appears it's using the same technology, so my question is there a simple way to add the same sort of redundancy to the api like Jiwa has?
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Users browsing this forum: No registered users and 2 guests