Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Jul 12, 2012

ODBC Connection Pool Management

Each ODBC DSN should have a unique and individual connection pool that is independent of the number of message flow instances and the number of nodes within those message flow instances that are referencing the DSN.

This independent connection pool should be manageable by the broker administrator.

Idea priority High
RFE ID 24459
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Aug 14, 2020

    As part of our regular commitment to reviewing RFEs, we have re-reviewed this RFE. We note that the architecture does allow you to idle out the connections and return them to the thread pool, but we agree that it would be helpful to allow an administrator to specify an exact desired number of threads for each connection, and to help display this by informing users of the linkage to which flows are using which database ODBC connections. We will continue to monitor this RFE. For now its status is maintained as Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Mar 24, 2013

    The situation is far more serious than described here, and there is more than ODBC-JDBC compatibility or max connection at stake. Currently, the state of affairs is as follows, to quote IBM: "the default behaviour of an ODBC connection used by an additional instance is to close as soon as that instance returns to the thread pool. That means the connection will close whenever the additional instance has no work to do. The connection can be configured to persist until the flow terminates."
    Further info:

    This means either maxing out on connections if they persist, or a continuous (and truly unnecessary) opening and closing of connections on a normal production system. We've monitored our databases and this is indeed the case - Our broker closes opens a new connection about three times per second. The repercussions for performance and scalability are obvious.

    IMO, this feature is a must.

  • Guest
    Dec 5, 2012

    Thanks for raising this requirement. We have a strategic desire to reach functional equivalence between ODBC and JDBC, and adding ODBC connection pooling is consistent with that aim. We'll investigate adding connection pooling for a follow-on release or fixpack.

  • Guest
    Jul 14, 2012

    The context here is to enable highly scalable connection management for Message Broker flows that need to connect directly to an ODBC database. Current functionality can mean that max database connections are quickly exhausted.