Skip to content

[AutoPR @azure/arm-marketplaceordering] Updating marketplace oredring with new version of Swagger#3246

Closed
openapi-sdkautomation[bot] wants to merge 2 commits intomasterfrom
sdkAuto/12469/@azure_arm-marketplaceordering
Closed

[AutoPR @azure/arm-marketplaceordering] Updating marketplace oredring with new version of Swagger#3246
openapi-sdkautomation[bot] wants to merge 2 commits intomasterfrom
sdkAuto/12469/@azure_arm-marketplaceordering

Conversation

@openapi-sdkautomation
Copy link
Copy Markdown

Create to sync Azure/azure-rest-api-specs#12469

Installation Instructions

You can install the package @azure/arm-marketplaceordering of this PR using the following command:

curl -L "https://portal.azure-devex-tools.com/api/sdk-dl-pub?p=Azure/12469/azure-sdk-for-js/@azure_arm-marketplaceordering/azure-arm-marketplaceordering-2.0.0.tgz" -o azure-arm-marketplaceordering-2.0.0.tgz
npm install azure-arm-marketplaceordering-2.0.0.tgz

Direct Download

The generated package can be directly downloaded from here:

@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/12469/@azure_arm-marketplaceordering branch 2 times, most recently from 5454bdc to 7bb19fd Compare January 21, 2021 14:10
@openapi-sdkautomation openapi-sdkautomation bot force-pushed the master branch 2 times, most recently from c01f5ad to d87b7b2 Compare January 26, 2021 01:18
HarshaNalluru and others added 2 commits January 26, 2021 01:54
## Bug
- `receiveMessages` method returned zero messages upon a connection refresh caused by a network disconnect(simulated in the test). 
- `OperationTimeout` error on message settlement after the disconnect

These two failures made the "disconnect" test occasionally fail for the batching receiver.

## Cause
`onDetached` on the batchReceivers is called 300ms after the connection refresh causing the recovered receive link to be closed.

- If the message returned from the service took close to 300ms until reached the receiver since the refresh, `onDetached` is called to close the link leading to the loss of messages.
- If the 300ms had elapsed right before the settlement, we'd see the OperationTimeout error on settlement since the receive link is closed.

Investigated here Azure#13339

## Fix
- Call `onDetached` for the batching receivers before calling the refresh connection
- And retain calling `onDetached` for the streaming receivers after the refresh connection

## Changes in the PR
- [x] Refactored "calling onDetached" part
- [x] Removed the 300ms delay since we don't see the utility
- [x] Changelog
- [x] TODO: What to do for sessions?
   - [x] Needs more investigation Azure#13374 (comment), will be handled at Azure#8875
Merge 05c6812b913d032d94495a41199825eb7f82eee6 into 9022265e19ebe2fa6c1955f6d99a51203897bf3d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant