Bug report

What Debezium connector do you use and what version?

PostgresConnector

What is the connector configuration?

debezium.sink.type=nats-jetstream
debezium.sink.nats-jetstream.url=nats://nats:4222
debezium.sink.nats-jetstream.subjects=CHANGELOG.event
debezium.format.value=json
debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
 debezium.source.offset.storage=org.apache.kafka.connect.storage.FileOffsetBackingStore

1. Redis offset store
   debezium.source.offset.storage=io.debezium.storage.redis.offset.RedisOffsetBackingStore
   debezium.source.offset.storage.redis.address=redis-master:6379
2. other config
   debezium.source.offset.flush.interval.ms=0
   debezium.source.database.hostname=postgresql-print-database
   debezium.source.database.port=5432
   debezium.source.database.user=postgres
   debezium.source.database.password=postgres
   debezium.source.database.dbname=print-dev
   debezium.source.database.server.name=print-dev
   debezium.source.plugin.name=pgoutput
   debezium.source.table.exclude.list=public.elasticsearch_queue_lock,public.databasechangelog
   debezium.source.slot.drop.on.stop=true
   debezium.source.snapshot.mode=never
   debezium.source.topic.prefix=print-api

   What is the captured database version and mode of depoyment?

local k8 with custom helm chart

What behaviour do you expect?

debezium publishes event to jetstream

What behaviour do you see?

`Error Publishing: 503 No Responders Available For Request`
even if nats cli lists specified stream subject

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

I tried 2.1.2, 2.1.1 and 2.1.0 all FINAL

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

debezium_debug_logs