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 IBM Event Automation
Categories Event Streams
Created by Guest
Created on Dec 13, 2024

RELATED IDEAS

Enhancement to the IBM MQ Source Connector to expose a two configurable values to adjust the blocking of the JMS receive methods when retrieving messages from MQ.

Opening this idea to expose two configurable parameters to IBM MQ Source Connector. We will like to have an configurable parameter to adjust the blocking wait time on the JMS receive() methods when the Connector task is getting messages from MQ.

Currently the connector will do an initial receive with a wait of 3 seconds for a message. If a message is returned back from MQ, any proceeding messages will be received using the receiveNoWait() method until no messages are returned. If a message is not returned, it will send a partial batch of messages to Kafka.  

We would like an enhancement that will allow us to configure both the initial and proceeding blocking.

  1. Initial receive  – allows to adjust the receive timeout for x (value time in ms) amount of time.
  2. Proceeding receive – allows to adjust the receive timeout for x (value time in ms) amount of time.
    1. If value is set to 0, do receiveNoWait() (default value of what it does today)
    2. If integer value greater than 0, do receive(<value time in ms>)

Reasons for this enhancement:

·         We found that during a batch of workload that is putting a message at a rate of 1 to 5 ms between puts was consistently sending partial batches of 1 to Kafka. This resulted in an increase in CPU usage because the connector was sending a single batch of messages to Kafka.

·         Increasing the timeout of the proceeding receive will allow to get a higher chance of filling up the batch of messages. Having a bigger batch size before sending to Kafka will increase performance, throughput and efficiency of the Connector.

·         Allowing adjustment to both the initial and proceeding receive will help reduce the number of “failed” GETs from MQ. Lowering the CPU usage on both MQ and the Connector.  

·         If it is an application that doesn’t have tight SLA, we would want to get as many full batches. Any business-critical application that requires no delay, we would configure to do a receive with no wait.

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.