Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
None
-
False
Description
Bug report
While the connector runs for sometime, it stops with the below error in sometime.
We are getting java.lang.IllegalArgumentException: Received event of unexpected command type: 4
Connector Log
streaming Producer failure [io.debezium.pipeline.ErrorHandler]
org.apache.kafka.connect.errors.ConnectException: Error while processing event at offset {transaction_id=null, event_serial_no=1, commit_lsn=00dbedff:d9fae65c:0800000000000001, change_lsn=00dbedff:d9f0be09:0000000000000005}
at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:255)
at io.debezium.connector.db2.Db2StreamingChangeEventSource.lambda$execute$1(Db2StreamingChangeEventSource.java:243)
at io.debezium.jdbc.JdbcConnection.prepareQuery(JdbcConnection.java:609)
at io.debezium.connector.db2.Db2Connection.getChangesForTables(Db2Connection.java:236)
at io.debezium.connector.db2.Db2StreamingChangeEventSource.execute(Db2StreamingChangeEventSource.java:153)
at io.debezium.connector.db2.Db2StreamingChangeEventSource.execute(Db2StreamingChangeEventSource.java:57)
at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:166)
at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:127)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalArgumentException: Received event of unexpected command type: 4
at io.debezium.connector.db2.Db2ChangeRecordEmitter.getOperation(Db2ChangeRecordEmitter.java:50)
at io.debezium.relational.RelationalChangeRecordEmitter.emitChangeRecords(RelationalChangeRecordEmitter.java:42)
at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:218)
... 12 more
What Debezium connector do you use and what version?
We are using debezium version 1.7
What is the connector configuration?
Few important connector config that we have are -
"connector.class": "io.debezium.connector.db2.Db2Connector",
"snapshot.mode": "schema_only",
"custom.cdc.program.schema": "ASNCDC",
"custom.db.type": "ZOS"
We have previously seen this kind of bug getting fixed for sqlserver but we do not find what changes were made to fix this in DB2 Connector.
Could you kindly let us know what possibly we might be missing.