ClientQueryTimeout triggers too early

We're using the 'ClientQueryTimeout' property to kill queries which are taking more than 60 seconds. The user will get this message: Timeout: The data took too long to load We're getting complaints from users that this message is triggered almost directly when accessing a form. We can't reproduce it, but it happens random and with almost every user. How is the query time determined by Mendix?
1 answers

Mendix creates a java.util.TimerTask for each JDBC statement and schedules it by a java.util.Timer immediately before the execution. The TimerTask cancels the query. This behavior is only used for PostgreSQL. The drivers for the other databases have built-in support via java.sql.Statement.setQueryTimeout(..).