Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

IBMi connector 3.3.0-SNAPSHOT

What is the connector configuration?

{
  "name": "xxx-1",
  "config":

{     "connector.class": "io.debezium.connector.db2as400.As400RpcConnector",     "tasks.max": "1",     "database.hostname": "xxx.xx.xx.xx",     "database.dbname": "xxxxxxx",     "port": "",     "database.user": "xxxxx",     "database.password": "xxxxx",     "database.from_ccsid": 37,     "database.to_ccsid": 285,     "database.driver.secure": true,     "database.secure": false,     "secure": false,     "database.schema": "xxx",     "poll.interval.ms": 2000,     "snapshot.mode": "initial",     "table.include.list": "xxx.DEMO",     "transforms": "unwrap,schemarename",     "transforms.schemarename.type": "com.fnz.kakfa.smt.RepackageJavaFriendlySchemaRenamer",     "transforms.schemarename.package": "com.fnz.debezium.schema",     "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",     "transforms.unwrap.drop.tombstones": "false",     "transforms.unwrap.delete.handling.mode": "rewrite",     "key.converter.schema.registry.url": "http://msschema-registry:8080/apis/ccompat/v7/",     "value.converter.schema.registry.url": "http://msschema-registry:8080/apis/ccompat/v7/",     "key.converter": "io.confluent.connect.avro.AvroConverter",     "value.converter": "io.confluent.connect.avro.AvroConverter",     "snapshot.max.threads": 4,     "topic.creation.default.cleanup.policy": "compact",     "topic.creation.default.retention.ms": -1,     "topic.creation.default.replication.factor": 1,     "topic.creation.default.partitions": 1,     "field.name.adjustment.mode": "avro",     "topic.prefix": "xxx.servers.jhc.co.uk",     "signal.enabled.channels": "source,kafka",     "signal.data.collection": "xxx.xxx.DEBEZIUM_SIGNAL",     "signal.kafka.topic": "xxx-1-signal",     "signal.kafka.bootstrap.servers": "mskafka:9092",     "signal.kafka.basic.auth.credentials.source": "USER_INFO"   }

}

What is the captured database version and mode of deployment?

N/A

What behavior do you expect?

Connector to start normally

What behavior do you see?

Error log on setting connector config:

java.lang.NullPointerException: Cannot invoke "java.time.Duration.compareTo(java.time.Duration)" because "d1" is null

  at io.debezium.time.Temporals.min(Temporals.java:32) ~[classes/:?]

  at io.debezium.connector.base.ChangeEventQueue.poll(ChangeEventQueue.java:283) ~[classes/:?]

  at io.debezium.connector.db2as400.As400ConnectorTask.doPoll(As400ConnectorTask.java:174) ~[classes/:?]

  at io.debezium.connector.common.BaseSourceTask.poll(BaseSourceTask.java:334) ~[classes/:?]

  at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.poll(AbstractWorkerSourceTask.java:466) ~[connect-runtime-3.9.0.jar:?]

  at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.execute(AbstractWorkerSourceTask.java:354) ~[connect-runtime-3.9.0.jar:?]

  at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:226) ~[connect-runtime-3.9.0.jar:?]

  at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:281) ~[connect-runtime-3.9.0.jar:?]

  at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.run(AbstractWorkerSourceTask.java:79) ~[connect-runtime-3.9.0.jar:?]

  at org.apache.kafka.connect.runtime.isolation.Plugins.lambda$withClassLoader$1(Plugins.java:238) ~[connect-runtime-3.9.0.jar:?]

  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]

  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]

  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]

  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]

  at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]

 

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

Yes, using latest release

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

Can be supplied

How to reproduce the issue using our tutorial deployment?

Occurs as soon as you submit a conifguration