Skip to content

Conversation

@ansd
Copy link
Member

@ansd ansd commented Mar 4, 2024

A follow-up to #9022.

@ansd ansd force-pushed the native-amqp-follow-ups branch from ef9ab12 to 1594518 Compare March 4, 2024 15:20
@ansd ansd marked this pull request as ready for review March 4, 2024 15:57
@michaelklishin michaelklishin added this to the 4.0.0 milestone Mar 4, 2024
@ansd
Copy link
Member Author

ansd commented Mar 4, 2024

Tests fail due to #10657

ansd added 3 commits March 4, 2024 11:32
If the server initiates the detach due to an error condition, it
destroys and therefore forgets the link.

This should be okay because accroding to section 2.6.5:
"When an error occurs at a link endpoint, the endpoint MUST be detached
with appropriate error information supplied in the error field of the detach
frame. The link endpoint MUST then be destroyed."

It is also valid that the client replies with a detach:
"If any input (other than a detach) related to the endpoint either via
the input handle or delivery-ids be received, the session MUST be
terminated with an errant-link session-error."

In this case, the server must not reply again with (i.e do not sent a 3rd)
detach.
for default and pre-declared exchanges to save copying
the #exchange{} record (i.e. save an ETS lookup call) on
every received message.

The default and pre-declared exchanges are protected from deletion and
modification. Exchange routing decorators are not used in tier 1 plugins
and in no open source tier 2 plugin.
when message was published to a stream via the stream protocol.

Fixes the following test:
```
./mvnw test -Dtest=AmqpInteroperabilityTest#publishToStreamConsumeFromStreamQueue
```
@michaelklishin michaelklishin force-pushed the native-amqp-follow-ups branch from 1594518 to 118d846 Compare March 4, 2024 16:32
@michaelklishin
Copy link
Collaborator

The forced push is a rebase.

@michaelklishin michaelklishin merged commit e590c9f into main Mar 4, 2024
@michaelklishin michaelklishin deleted the native-amqp-follow-ups branch March 4, 2024 16:48
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.

4 participants