We implement our applicaiton on JBoss Application Server.
To avoid endless running queries we use the "set-tx-query-timeout" flag. With this flag, on every statement setQueryTimeout will be used.
When having bigger load on the application, we use >120 db connections and sometimes execute thousands of statements per second.
This leeds to massive creation of threads and can even lead to an OutOfMemory. Debugging the application for example in Eclipse is not possible anymore.
We can just see this behaviour on the microsoft jdbc driver, on Oracle for example, a single thread is used to handle the query timeout
Please fix this issue as soon as possible and give us a date when we could have a solution for that.
There is already a feature request to this issue (https://connect.microsoft.com/SQLServer/feedback/details/669427/property-to-create-timer-threads-per-statement-or-connection-in-jdbc-driver), but in my opinion it is just a bug, that must be solved