Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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.


Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Jul 20, 2020

Provide an option that allows WebSphere Liberty database pool to maintain a minNumber of "warm" connections.

The current configuration options that are available in WLP do not allow for maintaining a minPoolSize number of connections in a given connection pool. Any events of connection aging (for example timeouts that can occur on the WLP side as well as on the Database side) will result in removing corresponding connection from the pool but will not proactively re-create a new connection in place of removed one.

This request proposes adding necessary logic to the pool management task that would proactively create new connections in the pool whenever the number of existing connections drops below min threshold.

Similar capability is present in other database pool implementations, for example Tomcat 9.

http://tomcat.apache.org/tomcat-9.0-doc/jdbc-pool.html

minIdle
(int) The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if validation queries fail. Default value is derived from initialSize:10 (also see testWhileIdle)[

Idea priority High
RFE ID 144070
RFE URL
RFE Product WebSphere Application Server
1 MERGED

Wait for application startup until datasources are ready.

Merged
Currently, the app is started as fast as possible. Datasource connections are initialized on first use. However, some applications need to use db connections right away. For this, each connection pool should have at least one connection ready when...
almost 2 years ago in WebSphere Liberty 0 Future consideration