Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Messaging] Update message size on link creation #44328

Merged
merged 1 commit into from
May 31, 2024

Conversation

jsquire
Copy link
Member

@jsquire jsquire commented May 30, 2024

Summary

The focus of these changes is to enable the client to refresh the maximum message size each time a new AMQP link is opened; this is necessary for large message support, where the maximum message size for entities can be reconfigred adjusted on the fly. Because the client had cached the value, it would not be aware of the change and would enforce the wrong size for batch creation.

References and related

The focus of these changes is to invalidate the
cached maximum message size when the link is created,
and populate with an updated value from the new link.

This is necessary for large message support, where
the maximum message size for entities can be
reconfigred adjusted on the fly.  Because the client
had cached the value, it would not be aware of the
change and would enforce the wrong size for batch
creation.
@jsquire jsquire added Service Bus Event Hubs Client This issue points to a problem in the data-plane of the library. labels May 30, 2024
@jsquire jsquire self-assigned this May 30, 2024
@jsquire
Copy link
Member Author

jsquire commented May 30, 2024

/azp run net - eventhub - tests

@jsquire
Copy link
Member Author

jsquire commented May 30, 2024

/azp run net - servicebus - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@jsquire jsquire merged commit 64654ff into Azure:main May 31, 2024
78 checks passed
@jsquire jsquire deleted the messaging/requery-max branch May 31, 2024 14:12
benbp pushed a commit that referenced this pull request Jun 5, 2024
The focus of these changes is to invalidate the
cached maximum message size when the link is created,
and populate with an updated value from the new link.

This is necessary for large message support, where
the maximum message size for entities can be
reconfigred adjusted on the fly.  Because the client
had cached the value, it would not be aware of the
change and would enforce the wrong size for batch
creation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs Service Bus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants