IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 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.

Additional Information

To view our roadmaps:

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

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Db2
Components Workload Management
Created by Guest
Created on Nov 29, 2021
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit DB24LUW-I-1408 Application connections storm slow downs the DB response.

Application connections storm slow downs the DB response Merged

I've been assisting with an ecommerce site. During typical days, let's say non-peak/low volume of orders, the DB response is always good.

However, the DB response time slows down for a few seconds, notably during peak season/high amount of orders.

BOOM !! it will ultimately happen whenever an application connection storm occurs !!

Let me explain a little about how DB/App is configured for this :

1. DB server is configured with high resources in terms of memory/CPU etc ..

NUM_POOLAGENTS and NUM_INITAGENTS with a value of 1000

2.The database had 168 established connections (14 JVMs x 12 connections).

Now with the JVMs' WebContainer pool completely saturated, the number of connections surged all the way to 600( 14 JVMs * 42 WebContainer threads = 600)

A connection storm was created in a matter of a second, and DB was unable to assign the delta new connections 360 on the fly. This resulted spikes in DB connection and reduced DB response time.

As we know, creating a connection has a cost. The database needs to handle the tcp connection, allocate memory and create the agent. If a large number of connection requests is received in a very short period of time, this can bog down the performance of the database to a point that it can appear to be unresponsive.

If we can play around with DB parameters like NUM_POOLAGENTS and NUM_INITAGENTS by keeping the values of 1000 , automatic etc doesn't help during the connection storm . The more connections to the database server, the slower the DB response is, which in turns drives even more new connections to the database.

During connection storm , I've noticed a lot of outbound connections with NULL values which means that most threads waiting on the outbound Web Service call

Example for connection storm :

No.of Connections

Peak /Non Peak

Jump and diff in DB connections


1st event


Non Peak - Low

ALL JVMs established connections

No spikes /DB response is GOOD

2nd event


Non Peak - Moderate


No spikes /DB response is GOOD

3rd event


Non Peak - High


No spikes /DB response is GOOD

4th event


Peak -LOW


A minimal spike /DB response is GOOD

5th event


Peak moderate


A spike with impacting DB response

6th event


Peak - High


A huge spike impacting DB response badly

Solution :

Nothing can be done at the database layer; just increase the number of JVM connections to the database during peak season, when the highest value is targeted.

Let's say in this scenario , just increase the number of established connections from 168 to 600 (14 JVMs x 12 connections) (14 JVMs x 42 connections). And maintain the largest number of connections in the database to manage the application storm.

Once peak season is over, re-configure the JVM connections to normal.

Needed By Not sure -- Just thought it was cool