We sometimes (about every two weeks) run into the problem that there are too many open connections to the datasource, so any new process that tries to execute an sql statement fails because he can't get another connection.
Our DB Connection Pool limit is 150 connections.
We have a hard time figuring out what is causing the problem. Is there a way in Appway to see which processes, threads, etc have connections to the DB open? How are DB connections handled by the DataStore Extension (which we use quite a lot)? What happens if you do sqlQuery (with datasource given), and what happens if you use sqlOpen and sqlClose? Is there any scenario in which connections stay open (after the query finished)?
We already checked that there are no sqlOpen statements without try/catch and a sqlClose in the finally statement.
We sometimes (about every two weeks) run into the problem that there are too many open connections to the datasource, so any new process that tries to execute an sql statement fails because he can't get another connection.
Our DB Connection Pool limit is 150 connections.
We have a hard time figuring out what is causing the problem. Is there a way in Appway to see which processes, threads, etc have connections to the DB open? How are DB connections handled by the DataStore Extension (which we use quite a lot)? What happens if you do sqlQuery (with datasource given), and what happens if you use sqlOpen and sqlClose? Is there any scenario in which connections stay open (after the query finished)?
We already checked that there are no sqlOpen statements without try/catch and a sqlClose in the finally statement.
Regards,
Tamara