Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace App Connect
Created by Guest
Created on Sep 14, 2026

RELATED IDEAS

ACE Resource connection aging by connection usage count - similar to maxConnectionUseCount, but not only to idle connections

Based on TS022758104 we would like to have a setting, where connections in a resource pool (database connections in our case) will be destroyed after a specific period of time independent of whether they are idle or not. Or by a specific usage count, similar to maxConnectionUseCount, but again not only applied on idle connections. 

We had this problem when connections were not destroyed after a HA failover of DB, because they were tried to be reused, but failing to process the data - remained connected to standby, which was read-only. This "activity" caused that they weren't idle, thus were never destroyed either.

Thank you for considering this idea.

Idea priority Low
  • Guest
    Sep 14, 2026

    As an alternative, it would be good to have an "agedConnectionTime" as is supported for WebSphere Liberty. Whenever a connection was used for longer than x Minutes, the connection has to be recreated and cannot be reused. This allows to recover from infrastructure issues, such as that during a HA-DR switch over the wrong IP was used and connection goes to wrong instance. 

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.