[ https://issues.apache.org/jira/browse/KAFKA-16311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hector Geraldino resolved KAFKA-16311. -------------------------------------- Resolution: Invalid Please try reporting this to [Debezium|https://github.com/debezium/debezium-connector-informix] https://issues.redhat.com/browse/DBZ > [Debezium Informix Connector Unable to Commit Processed Log Position] > --------------------------------------------------------------------- > > Key: KAFKA-16311 > URL: https://issues.apache.org/jira/browse/KAFKA-16311 > Project: Kafka > Issue Type: Bug > Reporter: Maaheen Yasin > Priority: Blocker > Attachments: connect logs.out > > > I am using Debezium Informix Source connector and JDBC Sink connector and the > below versions of Informix database and KAFKA Connect. > Informix Dynamic Server > 14.10.FC10W1X2 > Informix JDBC Driver for Informix Dynamic Server > 4.50.JC10 > KAFKA Version: 7.4.1-ce > > *Expected Behavior:* > All tasks of the Informix source connector are running, and all messages are > being published in the topic. During the DDL Execution, the informix 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. > *Actual Behavior:* > 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)* > > The complete KAFKA Connect logs has been attached. Kindly comment on why this > issue is occurring and what steps should be followed to avoid this issue or > to resolve this issue. > > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)