Integration


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 (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.


Add a new idea Subscribe
Status Submitted
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Oct 28, 2025

RELATED IDEAS

Fix the performance problem caused by regression for IT45058

After IT45058, the connection from MQ Java Client is serialized. This cause connection timeout to be processed serially, hence if there are many channels from MQ Java Client and connection timeout occur, the completion of timeout process for all channels takes too much times. For example, before IT45058, timeout process takes only 20 seconds (default timeout value) for 100 channels, but after IT45058, it takes 20 x 100 = 2000 secs, because timeout process is serialized respectively. This affects RTO (Recovery Time Objective) at failure scenarios that switch over to another QMGR. This problem can be avoided by setting "MQCNO_NO_CNV_SHARING" in Java property as workaround. However, MQ Java code must be fixed rather than workaround because of the following reasons.

1. This is clearly regression for IT45058

2. Workaround CANNOT be applied to the channels for SHARECNV>1, because MQCNO_NO_CNV_SHARING behave as SHARECNV(1)

TS018548302_202...
TS018548302_20250924.pptx
 TS018548302_20250924.pptx
Open full size
TS018548302_20250924.pptx
Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.