Hi, hopefully somebody here can give us some guidelines to fix or diagnose this issue since there little to none documentation on how Servoy deals with this.
Recently we received a notofication from our dba manager that a transaction created from our servoy application had a select query iddling and lockingup some tables. This prevented other users from accesing those tables. The idling started on a Friday and was detected on sunday when the culprit conection was killed. Our servoy dev team was required to ensure autocommit is set to true at all times which might solve this issue from happening but not sure how to achieve that from within servoy, probably we need to add a setting to our db conection setup within the servoy.properties file?. In our code transactions are commited on success or rolled back if they fail but there might be cases where users might disconnect in the middle of a transaction not reaching to the commit or roll back so the question is how does Servoy handle this cases?, Does Servoy autocommit when a conection is released back to the pool?
I would appreciate any help to guide what is the best way to avoid this scenario and also how to ensure PG autocommit is set to true from within Servoy.