Skip to Main Content
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.


Status Submitted
Categories Event Streams
Created by Guest
Created on Dec 13, 2024

Enhancement to the IBM MQ Source Connector JsonRecordBuilder to handle poison messages

Opening this idea to IBM MQ Source Connector JsonRecordBuilder. We will like the JsonRecordBuilder to be able to handle poison messages.

In the event an application puts a poisoned message (i.e incorrect JSON syntax payload), the connector task will go into a failed state. This requires manual intervention to find the bad message, remove the message, and restart the connector.

Some ideas for the connector to handle these poisoned messages, is to either:

·         Send the poison message to a backout queue

·         Send the poison message to a separate Kafka topic

This will allow the connector to proceed in processing valid messages. Sending the poison message to a different location will allow us to review the bad message.

In the event that poison messages occurs, either a warning or error message is written to connect log.

Idea priority Medium