Since upgrading our JBoss server, we sometimes we see thousands of Timer threads in the application server. Disabling QueryTimout is the current workaround
|Who would benefit from this IDEA?||As a customer I will be pleased by better performance while using less system resources for the JDBC driver, we can re-enable QueryTimeout as a safety net for protect against long-running queries in the database server.|
How should it work?
Instead of creating a new Timer object (which creates a new Thread) for each sql request, it should be possible to reuse either a singe Timer instance, or a fixed pool of Executors.
The benefits would be a faster driver with less resources, and still have the safety net of QueryTimeout
The current workaround is to disable QueryTimeout
|Priority Justification||We have OutOfMemory errors in production when QueryTimeout is enabled|
|Customer Name||PostNord AS|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions