Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Submitted
Created by Guest
Created on Dec 21, 2023

Terminate a long running txn on the MDM Operational Server when a set timeout is reached at the Client.

When MDM txns are executed on the Operational Server (getParty for example), the calling Client stays connected until receiving a SUCCESS or FAILURE response from the server. Once the response is received, the connection is closed.  In the case where the SERVER reponse takes longer than the timeout of the calling Client the CLIENT drops the connection and retries the txn  In the background the txn code on the SERVER is still running until it completes or fails.  The CLIENT retries, causing txns to pile up on the SERVER.  It is currently not possible to terminate the txn at the SERVER once it has been started.  It is desirable that in this case, the timeout of the MDM txn is respected AND the txn on the SERVER is terminated immediately to

1. Allow a retry and potentially a SUCCESSFUL outcome

2. Prevent the SERVER from being overwhelmed with ultimately FAILURE txns (as the client has timedout and will try again).

There are several thousands cases like this per day.  Many are handled SUCCESSFULLY.  Occasionally, the client timeout issue occurs and the server is left to struggle.

The proposed solution should allow:

For example, there are times when the DB is busy with other work and one of these potential long running GETs or ADDs or UPDATES is executed by the client app through an API call.  If the timeout is reached, take the following actions.

1.     For a GET txn, terminate immediately AND allow the client to retry, this is 90% of the long running txns.  Potentially, when the client retries the DB is able to SUCCESSFULLY service the request.

2.     For an ADD / UPDATE or DELETE txn, terminate immediately AND release the DB to allow a later SUCCESSFUL retry.

The current experience is that during peak demands, these long running calls fail (7s timeout is standard across the calling applications) and are then subject to a retry at the client side, whilst the Server side is still busy with the timedout txn.

Needed By Not sure -- Just thought it was cool