Product and version: FileMaker 16 JDBC driver
Description: I have a table with lots of records in it and it takes a while for the server to respond to a query like "SELECT * FROM big_table" through JDBC. It causes connection leaking when using Hibernate to access the datasource. Why does filemaker ignore the javax.persistence.query.timeout parameter?
How to replicate: make a select query without constraints to a big table with calculated fields through JDBC.
Workaround: Override the FM JDBC driver's connect method and include the SockeTtimeout parameter into the properties. When the FM server is not responding, data are not coming from the socket causing an exception, closing and releasing the connection preventing the leak.