Skip to content

Conversation

@ansd
Copy link
Member

@ansd ansd commented Aug 4, 2025

RabbitMQ MAY initialise the next-outgoing-id and delivery-count sequence numbers to arbitrary values.

For RabbitMQ 4.2, let's initialise both to 0.
This allows clients using an old amqpnetlite library (i.e. clients which haven't yet upgraded to a version containing the fixes for Azure/amqpnetlite#575 and Azure/amqpnetlite#578) to be used with RabbitMQ 4.2.

@ansd ansd self-assigned this Aug 4, 2025
@ansd ansd changed the title Initialise outgoing transfer-id to 0 Initialise sequence numbers to 0 Aug 5, 2025
@ansd ansd added this to the 4.2.0 milestone Aug 5, 2025
@ansd ansd marked this pull request as ready for review August 5, 2025 15:00
@ansd ansd requested a review from kjnilsson August 5, 2025 15:00
@michaelklishin
Copy link
Collaborator

To add some context: this will allow certain systems that use amqpnetlite very heavily upgrade from 3.13.x to 4.2.x without upgrading the [buggy] client version in lock step.

@michaelklishin michaelklishin merged commit df2dd96 into main Aug 5, 2025
557 of 561 checks passed
@michaelklishin michaelklishin deleted the initial-transfer-id branch August 5, 2025 15:09
@michaelklishin
Copy link
Collaborator

This 4.2.0 alpha release includes this change.

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.

3 participants