-
Bug
-
Resolution: Done
-
Major
-
2.5.0.Alpha1, 2.5.0.Alpha2
-
None
-
False
-
None
-
False
Bug report
What Debezium connector do you use and what version?
debezium-connector-informix:2.5.0-Alpha1
What is the connector configuration?
{
"connector.class": "io.debezium.connector.informix.InformixConnector",
"database.hostname": hostname,
"database.port": port,
"database.user": username,
"database.password": password,
"database.dbname": dbname,
"topic.prefix": "topic.prefix",
"table.include.list": "...",
"tombstones.on.delete": false,
"include.schema.changes": false,
"schema.name.adjustment.mode": "avro",
"field.name.adjustment.mode": "avro",
"sanitize.field.names": true,
"snapshot.mode": "initial",
"snapshot.isolation.mode": "exclusive",
"event.processing.failure.handling.mode": "warn",
"provide.transaction.metadata": true,
"signal.data.collection": "debezium_signal",
"signal.enabled.channels": "source,kafka",
"signal.kafka.topic": "topic.prefix.debezium_signal",
"signal.kafka.bootstrap.servers": ...,
"schema.history.internal.kafka.topic": "legacy.privat.schemahistory",
"schema.history.internal.kafka.bootstrap.servers": ...,
"schema.history.internal.skip.unparseable.ddl": true,
"schema.history.internal.store.only.captured.tables.ddl": false,
"schema.history.internal.store.only.captured.databases.ddl": true,
"errors.log.enable": true,
"errors.log.include.messages": true
}
What is the captured database version and mode of depoyment?
On-prem. Informix 12.10 and local docker
informix-developer-database:12.10.FC12W1DE
What behaviour do you expect?
Successfull start of connector instance
What behaviour do you see?
Connector task fails with below printout:
org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped. at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:67) at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:144) 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: io.debezium.DebeziumException: java.util.concurrent.ExecutionException: org.apache.kafka.connect.errors.ConnectException: Failed reading CURRENT_TIMESTAMP from source database at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:101) at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:253) at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:237) at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:189) at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:137) ... 5 more Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.connect.errors.ConnectException: Failed reading CURRENT_TIMESTAMP from source database at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) at io.debezium.relational.RelationalSnapshotChangeEventSource.createDataEvents(RelationalSnapshotChangeEventSource.java:463) at io.debezium.relational.RelationalSnapshotChangeEventSource.doExecute(RelationalSnapshotChangeEventSource.java:165) at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:92) ... 9 more Caused by: org.apache.kafka.connect.errors.ConnectException: Failed reading CURRENT_TIMESTAMP from source database at io.debezium.relational.RelationalSnapshotChangeEventSource.getSnapshotSourceTimestamp(RelationalSnapshotChangeEventSource.java:503) at io.debezium.relational.RelationalSnapshotChangeEventSource.doCreateDataEventsForTable(RelationalSnapshotChangeEventSource.java:538) at io.debezium.relational.RelationalSnapshotChangeEventSource.lambda$createDataEventsForTableCallable$6(RelationalSnapshotChangeEventSource.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ... 5 more Caused by: java.sql.SQLSyntaxErrorException: A syntax error has occurred. at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:413) at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:400) at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3023) at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3274) at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) at com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1442) at com.informix.jdbc.IfxResultSet.executeQuery(IfxResultSet.java:183) at com.informix.jdbc.IfxStatement.executeQueryImpl(IfxStatement.java:909) at com.informix.jdbc.IfxStatement.executeQuery(IfxStatement.java:169) at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:626) at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:495) at io.debezium.connector.informix.InformixConnection.getCurrentTimestamp(InformixConnection.java:107) at io.debezium.relational.RelationalSnapshotChangeEventSource.getSnapshotSourceTimestamp(RelationalSnapshotChangeEventSource.java:495) ... 8 more
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
Yes
How to reproduce the issue using our tutorial deployment?
In tutorial/debezium-ifx-init/ifxserver/Dockerfile replace
FROM icr.io/informix/informix-developer-database:14.10.FC9W1DE
with
FROM ibmcom/informix-developer-database:12.10.FC12W1DE
and run the example.