kafka-connect-mq-sink icon indicating copy to clipboard operation
kafka-connect-mq-sink copied to clipboard

MQ Manager ( Ver: 7.5.0.6) not receiving JMSCorrelationID

Open jobykurianiag opened this issue 1 year ago • 2 comments

Hello,

We are using "Kafka connect mq sink" for sending message from AWS MSK Topic to MQ Manager (WebSphere MQ Ver: 7.5.0.6). The connector deployed in ECS Fargate. We are using below config to send message, unfortunately MQ Manager not receiving "JMSCorrelationID".

Kafka - AWS MSK Connector version - v1.5.2 Task - AWS ECS Service

mq-sink.json

{ "name": "name-sink", "config": { "connector.class": "com.ibm.eventstreams.connect.mqsink.MQSinkConnector", "tasks.max": "1", "topics": "topic name",
"key.converter": "org.apache.kafka.connect.storage.StringConverter", "value.converter": "org.apache.kafka.connect.storage.StringConverter", "mq.queue.manager": "XXXX", "mq.connection.name.list": "XXXX", "mq.channel.name": "XXXXX", "mq.queue": "XXXXX", "mq.message.body.jms": "false", "mq.message.builder": "com.ibm.eventstreams.connect.mqsink.builders.DefaultMessageBuilder", "mq.message.builder.key.header": "JMSCorrelationID", "offset.storage.file.filename": "", "mq.userid":"XXXXX" } }

But when we sent same message to another MQ Manager with latest version (IBM MQ v9.2), it is working for them (they are receiving "JMSCorrelationID" as part of message).

  1. Is there any minimum version requirement for MQ Manager, in order to use mq sink connector ?
  2. If MQ Version is not supported, is there any alternative option to send "JMSCorrelationID" ?

jobykurianiag avatar Oct 10 '24 09:10 jobykurianiag