Bug: Destination connector stop working after NATS reconnection

[Nassor Paulino da Silva]

Bug description

After the NATS system recreates a connection, the destination connector ceases to function by not being able to write to the new nats connection.

Steps to reproduce

• Start the connector and NATS server.
• Create a pipeline file with NATS Jetstream as the source and destination
• Run nats bench test --js --storage=memory --pub 1 --size 32 --msgs=200000 to send msgs to NATS
• Run conduit and observe by running nats bench test --js --sub=1 --pull
• Stop NATS server
• Stop NATS benchmark
• Start NATS server
• Send more messages
• Start NATS benchmark
• Observe logs of messages that stop reaching the destination.

Version

v0.3.1