Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

I am using Debezium Informix Source connector, and the version is 2.6.0. 

What is the connector configuration?

{     "connector.class": "io.debezium.connector.informix.InformixConnector",     "errors.log.include.messages": "true",     "topic.creation.default.partitions": "1",     "value.converter.schema.registry.subject.name.strategy": "io.confluent.kafka.serializers.subject.TopicNameStrategy",     "tasks.max": "1",     "key.converter.schema.registry.subject.name.strategy": "io.confluent.kafka.serializers.subject.TopicNameStrategy",     "transforms": "unwrap,TSF1",     "transforms.TSF1.static.field": "instance_id",     "errors.deadletterqueue.context.headers.enable": "true",     "database.connection.retry.interval.ms": "1000",     "schema.history.internal.store.only.captured.tables.ddl": "true",     "schema.history.internal.store.only.captured.databases.ddl": "true",     "transforms.TSF1.type": "org.apache.kafka.connect.transforms.InsertField$Value",     "tombstones.on.delete": "true",     "topic.prefix": "mcp_kafka_net_21",     "decimal.handling.mode": "double",     "schema.history.internal.kafka.topic": "informixschemahistory",     "transforms.unwrap.drop.tombstones": "false",     "topic.creation.default.replication.factor": "1",     "errors.deadletterqueue.topic.replication.factor": "1",     "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",     "value.converter": "io.confluent.connect.avro.AvroConverter",     "errors.log.enable": "true",     "key.converter": "io.confluent.connect.avro.AvroConverter",     "database.user": "kafka",     "database.dbname": "cards_1952",     "topic.creation.default.compression.type": "lz4",     "topic.creation.default.cleanup.policy": "compact",     "time.precision.mode": "connect",     "database.server.name": "mcp_kafka_net_21",     "snapshot.isolation.mode": "read_committed",     "schema.history.internal.kafka.bootstrap.servers": "192.168.151.201:9092,192.168.151.202:9092,192.168.151.203:9092",     "database.port": "9260",     "value.converter.schema.registry.url": "http://192.168.151.201:8081",     "transforms.TSF1.static.value": "150",     "errors.max.retries": "10",     "database.hostname": "192.168.151.101",     "errors.deadletterqueue.topic.name": "informix-gpdb-source-errors",     "database.connection.retries": "5",     "database.password": "******",     "errors.tolerance": "all",     "table.include.list": "cards_1952.mcp.trans_requests_reps",     "pk.mode": "primary_key",     "key.converter.schema.registry.url": "http://192.168.151.201:8081",     "snapshot.mode": "schema_only" }

What is the captured database version and mode of deployment?

I am using the below versions of Informix and I am using the KAFKA Connect UI for Debezium connector deployment. 

 

Informix Dynamic Server
14.10.FC10W1X2
Informix JDBC Driver for Informix Dynamic Server
4.50.JC10

KAFKA Version: 7.4.1-ce

What behaviour do you expect?

All tasks of the Informix source connector are running, and all messages are being published in the topic. During the DDL Execution, the database is put under single user mode and the DDL on the table on which CDC was previously enabled was executed. After the database exits from the single user mode, then the connector should be able to reconnect with the source database and be able to publish messages in the topic for each new event. 

What behaviour do you see?

All tasks of the Informix source connector are running, and all messages are being published in the topic. During the DDL Execution, the database is put under single user mode and the DDL on the table on which CDC was previously enabled was executed. After the database exits from the single user mode, the source connector is able to reconnect with the database, however, no messages are being published in the topic and the below error is being printed in the KAFKA Connect Logs. 

 

[2024-02-22 15:54:34,913] WARN [kafka_devs|task-0|offsets] Couldn't commit processed log positions with the source database due to a concurrent connector shutdown or restart (io.debezium.connector.common.BaseSourceTask:349)

Do you see the same behaviour using the latest relesead Debezium version?

Yes, the same issue is occurring for when the informix jar files has been updated to 2.6.0 Alpha2. 

Do you have the connector logs, ideally from start till finish?

The complete KAFKA Connect logs has been attached.