I am getting the error below every now and then from my server program. It is running on a windows server vps and the database I am using is postgres rather than mysql.
When I get this error I have to restart the server program to get it working again.
This is happening during my testing when there is a very light load on the server, a remote app (ie on my computer) makes requests every 30 seconds while I am making the odd request as well from a browser.
The vps is entry level and has only 2GB of RAM and one virtual processor so maybe that might be an issue.
I don't think I am leaving any connections open, For all subs doing database access the pattern i use is
So I was wondering if there could be an issue with connection pooling not working with postgres so well, the version of postgres I am using is 9.4
com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@4d154ccd -- timeout at awaitAvailable()
When I get this error I have to restart the server program to get it working again.
This is happening during my testing when there is a very light load on the server, a remote app (ie on my computer) makes requests every 30 seconds while I am making the odd request as well from a browser.
The vps is entry level and has only 2GB of RAM and one virtual processor so maybe that might be an issue.
I don't think I am leaving any connections open, For all subs doing database access the pattern i use is
B4X:
Private Sub etc
Dim sql1 As SQL = Main.pool.GetConnection
Dim rs as resultset
Try
'do stuff
Catch
Log(LastException.message)
End Try
rs.Close
sql1.Close
End Sub
So I was wondering if there could be an issue with connection pooling not working with postgres so well, the version of postgres I am using is 9.4