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

Receiver error amqp:session:window-violation after upgrading to RabbitMQ 4 #426

Open
Marshall-ProRata opened this issue Sep 19, 2024 · 2 comments

Comments

@Marshall-ProRata
Copy link

Hello!

I'm able to successfully set up a receiver using the receive.ts test script (in this repo) against a Docker instance of RabbitMQ 3 with the amqp 1.0 plugin loaded.

I upgraded to RabbitMQ 4, which has amqp natively built into the image and no longer needs the plugin.

However, it bombs out with a window-violation error:

rabbitmq-1  | [info] <0.2195.0> Connection from AMQP 1.0 container <uid>: user 'guest' authenticated using SASL mechanism PLAIN and granted access to vhost '/'
rabbitmq-1  | [warning] <0.2200.0> Closing session for connection <0.2195.0>: {'v1_0.error',
rabbitmq-1  | [warning] <0.2200.0>                                             {symbol,
rabbitmq-1  | [warning] <0.2200.0>                                              <<"amqp:session:window-violation">>},
rabbitmq-1  | [warning] <0.2200.0>                                             {utf8,
rabbitmq-1  | [warning] <0.2200.0>                                              <<"next-incoming-id from FLOW (0) leads next-outgoing-id (4294967292)">>},
rabbitmq-1  | [warning] <0.2200.0>                                             undefined}

Any idea how I can fix this? Thanks!

@grs
Copy link
Member

grs commented Sep 19, 2024

should be fixed by #427

@Marshall-ProRata
Copy link
Author

Awesome, I just tried it against version 4 and it's fixed!

Thanks for the quick turn-around!

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

No branches or pull requests

2 participants