Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-1256

Connect Postgres - NullPointerException at io.debezium.time.Conversions.toEpochMicros

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • 0.9.4.Final
    • postgresql-connector
    • None
    • Hide

      connector.class=io.debezium.connector.postgresql.PostgresConnector
      database.dbname=XXX
      database.user=XXX
      max.queue.size=131072
      slot.name=XXX
      schema.compatibility=NONE
      tasks.max=5
      database.server.name=XXX
      offset.flush.timeout.ms=60000
      database.port=5432
      plugin.name=wal2json_rds_streaming
      offset.flush.interval.ms=5000
      value.converter.schema.registry.url=XXX
      decimal.handling.mode=double
      database.hostname=XXX
      database.password=XXX
      max.batch.size=32768
      value.converter=io.confluent.connect.avro.AvroConverter
      key.converter=io.confluent.connect.avro.AvroConverter
      key.converter.schema.registry.url=XXX
      rows.fetch.size=40960
      snapshot.lock.timeout.ms=99999999
      snapshot.mode=initial

      Start the connector with above configs, getting error after sometime, doesn't fix by restarting the task/connector/connect process

      Show
      connector.class=io.debezium.connector.postgresql.PostgresConnector database.dbname=XXX database.user=XXX max.queue.size=131072 slot.name=XXX schema.compatibility=NONE tasks.max=5 database.server.name=XXX offset.flush.timeout.ms=60000 database.port=5432 plugin.name=wal2json_rds_streaming offset.flush.interval.ms=5000 value.converter.schema.registry.url=XXX decimal.handling.mode=double database.hostname=XXX database.password=XXX max.batch.size=32768 value.converter=io.confluent.connect.avro.AvroConverter key.converter=io.confluent.connect.avro.AvroConverter key.converter.schema.registry.url=XXX rows.fetch.size=40960 snapshot.lock.timeout.ms=99999999 snapshot.mode=initial Start the connector with above configs, getting error after sometime, doesn't fix by restarting the task/connector/connect process

    Description

      I am getting this error in my source Postgres connector, (AWS RDS Version: 10.4, Debezium Version: 0.9.4Final)

      Please assist at the earliest, thanks already!

      org.apache.kafka.connect.errors.ConnectException: An exception ocurred in the change event producer. This connector will be stopped.
	at io.debezium.connector.base.ChangeEventQueue.throwProducerFailureIfPresent(ChangeEventQueue.java:170)
	at io.debezium.connector.base.ChangeEventQueue.poll(ChangeEventQueue.java:151)
	at io.debezium.connector.postgresql.PostgresConnectorTask.poll(PostgresConnectorTask.java:161)
	at org.apache.kafka.connect.runtime.WorkerSourceTask.poll(WorkerSourceTask.java:244)
	at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:220)
	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)
	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
	at io.debezium.time.Conversions.toEpochMicros(Conversions.java:239)
	at io.debezium.connector.postgresql.SourceInfo.update(SourceInfo.java:199)
	at io.debezium.connector.postgresql.RecordsStreamProducer.process(RecordsStreamProducer.java:252)
	at io.debezium.connector.postgresql.RecordsStreamProducer.lambda$streamChanges$1(RecordsStreamProducer.java:134)
	at io.debezium.connector.postgresql.connection.wal2json.StreamingWal2JsonMessageDecoder.doProcessMessage(StreamingWal2JsonMessageDecoder.java:242)

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. DBZ-1241 NullpointerException due to optional value for commitTime

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              pranav.mnnit@gmail.com Pranav Agrawal (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: