Error while attempting to Setting resume token: No value present (io.debezium.connector.mongodb.connection.MongoDbConnections:52) #1643
Description
Bug report
What Debezium connector do you use and what version?
debezium-connector-mongodb-3.4.1.Final-plugin.tar.gz
What is the connector configuration?
{
"name": "dbz-mongo-json-cdc-src",
"config": {
"buffer.memory": 16777216,
"capture.mode": "change_streams_update_full",
"capture.scope": "collection",
"collection.include.list": "database.coll1,database.coll2,database.coll3,database.coll4,database.coll5,database.coll6,database.coll7",
"connector.class": "io.debezium.connector.mongodb.MongoDbConnector",
"key.converter": "org.apache.kafka.connect.json.JsonConverter",
"key.converter.schemas.enable": false,
"max.record.size": 16777216,
"message.max.bytes": 16777216,
"mongodb.connection.string": "mongodb+srv://REDACTED.mongodb.net/?tls=true&authSource=%24external&authMechanism=MONGODB-AWS",
"mongodb.members.auto.discover": true,
"mongodb.ssl.enabled": true,
"producer.override.max.request.size": 16777216,
"publish.full.document.only": true,
"signal.enabled.channels": "kafka",
"signal.kafka.bootstrap.servers": "REDACTED.confluent.cloud:9092",
"signal.kafka.topic": "vkc.cdc.mongodb.json.v1._signal",
"snapshot.mode": "initial",
"tasks.max": 1,
"topic.creation.default.partitions": "3",
"topic.creation.default.replication.factor": "3",
"topic.creation.enable": true,
"topic.prefix": "vkc.cdc.mongodb.json.v1",
"value.converter": "org.apache.kafka.connect.json.JsonConverter",
"value.converter.schemas.enable": false
}
}
What is the captured database version and mode of deployment?
MongoDB Atlas, version 8.0.19. The cluster in question has two shards currently.
What behavior do you expect?
Expected to be able to take snapshots from the indicated MongoDB collections.
What behavior do you see?
Instead we get the following, seemingly fatal, error:
[2026-02-23 16:11:43,637] ERROR Error while attempting to Setting resume token: No value present (io.debezium.connector.mongodb.connection.MongoDbConnections:52)
java.util.NoSuchElementException: No value present
Do you see the same behaviour using the latest released Debezium version?
Yes, as we are running the latest released version already. We have not tried any pre-release versions as of yet.
Do you have the connector logs, ideally from start till finish?
Yes, but only at INFO level at the moment. If necessary, I can get DEBUG or TRACE level logs.
How to reproduce the issue using our tutorial deployment?
Neither the MongoDB cluster nor the Kafka broker in question would be available for use with this.