Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on May 19, 2022
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit TWAS-I-229 Provide an option that allows WebSphere Liberty database pool to maintain a minNumber of "warm" connections..

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 the application is started.

For this, there should be a property. Either at the datasource or application level, e.g. "<application waitForDatasources="5s"> (where 5s is the max waiting time).

Liberty would then open a connection and try to do a simple "SELECT 1 FROM SYSIBM.SYSDUMMY1" (for IBM DB2) or "SELECT 1 FROM DUAL" (for Oracle) etc.

"SELECT 1" should work for most other databases.

Idea priority High