https://github.com/epomatti/servicebus-timeout
Service Bus Node.js SDK bug simulation
https://github.com/epomatti/servicebus-timeout
az-300 azure disconnect nodejs servicebus timeout
Last synced: 3 months ago
JSON representation
Service Bus Node.js SDK bug simulation
- Host: GitHub
- URL: https://github.com/epomatti/servicebus-timeout
- Owner: epomatti
- License: mit
- Created: 2020-03-30T15:09:30.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2024-11-19T15:30:37.000Z (6 months ago)
- Last Synced: 2025-01-17T18:36:53.962Z (4 months ago)
- Topics: az-300, azure, disconnect, nodejs, servicebus, timeout
- Language: JavaScript
- Homepage:
- Size: 98.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Azure Service Bus Timeout
Sample code created to demonstrate my issue [#7689](https://github.com/Azure/azure-sdk-for-js/issues/7689) with Service Bus Node.js SDK for a bug that locked the receiver when the internet was unavailable for long periods of time.
> ✅ This bug has since been fixed by Microsoft
### Infrasctructure
```sh
az servicebus namespace create -n '' -g '' -l '' --sku Basic
az servicebus queue create -n '' --namespace-name '' -g ''
az servicebus namespace authorization-rule keys list \
-n RootManageSharedAccessKey -g '' --namespace-name '' \
--query primaryConnectionString -o tsv
```
### Simulation
Create `.env` and fill with environment values:
```sh
cp config/sample.env .env
```
Run it:
```sh
yarn install
yarn run dequeue
```
Now disconnect your computer from the internet and wait at least `1:20` minutes.
Reconnect to the internet and add messages to confirm it continues to operate:
```sh
yarn run enqueue
```
All messages should be consumed.