Keeping Service Bus Connection alive for duration of app lifecycle - node.js

Question

Hi I am using the new nodejs sdk to connect to servicebus. What is the proper way to keep receiving messages as long as my application is running? The example code shows 2 ways of listening for messages:
Method 1 - Receive Batch
const receiver = client.getReceiver();
try {
for (let i = 0; i < 10; i++) {
const messages = await receiver.receiveBatch(1, 5);
if (!messages.length) {
console.log("No more messages to receive");
break;
}
console.log(`Received message #${i}: ${messages[0].body}`);
await messages[0].complete();
}
await client.close();
} finally {
await ns.close();
}
}
Method 2 - Streaming Listener
try {
receiver.receive(onMessageHandler, onErrorHandler, { autoComplete: false });
// Waiting long enough before closing the receiver to receive messages
await delay(5000);
await receiver.close();
await client.close();
} finally {
await ns.close();
}
I went with method 2, on startup, and basically never close the client. But after a period of time the connection just stops working and the messages don't get received anymore (stuck in the queue).
What is the correct way to receive messages "forever"?:
Re-establish a new client (open and close eg every minute) with method 1, OR
Re-establish a new client (open and close eg every minute) with method 2, OR
Some kind of polling system (how)?

Answer 1

I know this is a late reply, but... Version 7 of #azure/service-bus SDK offers a solution in order to tackle this specific problem of disconnects and reconnection.
The subscribe method(which is equivalent to the receive method in your code snippet) can be leveraged which would run forever and is capable of recovering from fatal errors as well.
You can refer to the receiveMessagesStreaming.ts sample code that uses version 7 of #azure/service-bus SDK.
The latest version 7.0.0 of #azure/service-bus has been released recently.
#azure/service-bus - 7.0.0
Samples for 7.0.0
Guide to migrate from #azure/service-bus v1 to v7