-
Bug
-
Resolution: Unresolved
-
Major
-
2.1.2.Final
-
None
-
False
-
None
-
False
-
Moderate
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.1.2
What is the connector configuration?
connector.class: "" database.hostname: "" database.port: "" database.dbname: "" database.user: "" database.password: database.server.name: "" table.include.list: "" schema.history.internal.kafka.topic: "schemahistory.test" schema.history.internal.kafka.bootstrap.servers: topic.creation.default.replication.factor: 3 offsets.topic.replication.factor: 3 group.initial.rebalance.delay.ms: 3 key.converter: "org.apache.kafka.connect.json.JsonConverter" key.converter.schemas.enable: "false" topic.prefix: snapshot.mode: "initial" time.precision.mode: "connect" include.schema.changes: "false" topic.creation.default.partitions: 3 value.converter: "org.apache.kafka.connect.json.JsonConverter" value.converter.schemas.enable: "false" decimal.handling.mode: "string" tombstones.on.delete: "false" database.history.consumer.security.protocol: "SASL_SSL" schema.history.internal.consumer.security.protocol: "SASL_SSL" schema.history.internal.consumer.ssl.endpoint.identification.algorithm: "https" schema.history.internal.consumer.sasl.mechanism: "PLAIN"
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
ASNCDC capture for DB2 and AWS Kubernetes deployment
What behaviour do you expect?
Should have processed the data
What behaviour do you see?
Failed to process a even which was already earlier processed by Debezium. Getting this error.
Character is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Stopping down connector (io.debezium.connector.common.BaseSourceTask) [task-thread-db2-connector-finopengovdemo-stwapdb-0]2023-11-02 15:19:13.519 ... 13 more2023-11-02 15:19:13.519 at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:224)2023-11-02 15:19:13.519 at io.debezium.relational.RelationalChangeRecordEmitter.emitChangeRecords(RelationalChangeRecordEmitter.java:53)2023-11-02 15:19:13.519 at io.debezium.relational.RelationalChangeRecordEmitter.emitUpdateRecord(RelationalChangeRecordEmitter.java:99)2023-11-02 15:19:13.519 at io.debezium.relational.TableSchema.keyFromColumnData(TableSchema.java:130)2023-11-02 15:19:13.519 at io.debezium.relational.TableSchemaBuilder.lambda$createKeyGenerator$3(TableSchemaBuilder.java:204)2023-11-02 15:19:13.519 at io.debezium.jdbc.JdbcValueConverters.lambda$converter$11(JdbcValueConverters.java:310)2023-11-02 15:19:13.519 at io.debezium.jdbc.JdbcValueConverters.convertDecimal(JdbcValueConverters.java:1058)2023-11-02 15:19:13.519 at io.debezium.jdbc.JdbcValueConverters.toBigDecimal(JdbcValueConverters.java:1067)2023-11-02 15:19:13.519 at io.debezium.jdbc.JdbcValueConverters.convertValue(JdbcValueConverters.java:1331)2023-11-02 15:19:13.519 at io.debezium.jdbc.JdbcValueConverters.lambda$toBigDecimal$46(JdbcValueConverters.java:1090)2023-11-02 15:19:13.519 at java.base/java.math.BigDecimal.<init>(BigDecimal.java:900)2023-11-02 15:19:13.519 at java.base/java.math.BigDecimal.<init>(BigDecimal.java:471)2023-11-02 15:19:13.519 at java.base/java.math.BigDecimal.<init>(BigDecimal.java:586)2023-11-02 15:19:13.519Caused by: java.lang.NumberFormatException: Character is neither a decimal digit number, decimal point, nor "e" notation exponential mark.2023-11-02 15:19:13.519 ... 9 more2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2StreamingChangeEventSource.execute(Db2StreamingChangeEventSource.java:161)2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2Connection.getChangesForTables(Db2Connection.java:178)2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2Connection.prepareQuery(Db2Connection.java:448)2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2StreamingChangeEventSource.lambda$execute$1(Db2StreamingChangeEventSource.java:244)2023-11-02 15:19:13.519 at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:261)2023-11-02 15:19:13.519Caused by: org.apache.kafka.connect.errors.ConnectException: Error while processing event at offset {transaction_id=null, event_serial_no=2, commit_lsn=00000000:005090be:00000000015fa23b, change_lsn=00000000:00000000:000000035e12697c}2023-11-02 15:19:13.519 at java.base/java.lang.Thread.run(Thread.java:833)2023-11-02 15:19:13.519 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)2023-11-02 15:19:13.519 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)2023-11-02 15:19:13.519 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)2023-11-02 15:19:13.519 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)2023-11-02 15:19:13.519 at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:109)2023-11-02 15:19:13.519 at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:141)2023-11-02 15:19:13.519 at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:174)2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2StreamingChangeEventSource.execute(Db2StreamingChangeEventSource.java:59)2023-11-02 15:19:13.519 at io.debezium.connector.db2.Db2StreamingChangeEventSource.execute(Db2StreamingChangeEventSource.java:267)2023-11-02 15:19:13.519 at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:53)2023-11-02 15:19:13.519org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
How to reproduce the issue using our tutorial deployment?
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
<Your answer>