IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Don't create new Timer threads for each query in the JDBC driver when query timeout is enabled

Since upgrading our JBoss server, we sometimes we see thousands of Timer threads in the application server. Disabling QueryTimout is the current workaround

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 17 2020
  • Submitted
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

Idea Priority High
Priority Justification We have OutOfMemory errors in production when QueryTimeout is enabled
Customer Name PostNord AS
  • Attach files

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 "anonymous@euprivacy.out" 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