You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connecting to amqp with channel_max value of 0 is no longer allowed.
failed to negotiate connection parameters: negotiated channel_max = 0 (no limit) is higher than the maximum allowed value (2047)
I bypassed this by setting channel_max to 0 in rabbitmq, but this is not ideal.
The third parameter to amqp_login should be changed
amqp_login(amqpConn, "/", 0, ...
The text was updated successfully, but these errors were encountered:
bcb
changed the title
Can't connect: channel_max higher than the maximum allowed value
Error: channel_max higher than the maximum allowed value
Sep 1, 2020
bcb
changed the title
Error: channel_max higher than the maximum allowed value
Channel_max higher than the maximum allowed value
Sep 1, 2020
Thank you for reporting this. I will have a look and make a patch.
On another note you might be interested to have a look at https://github.com/olesku/eventhub which is serving the same purpose as ssehub but using websockets instead. It has a lot more functionality, is bi-directional, battle tested in production and under active development.
It also has SSE support, but not as it's main citizen and implemented more as a backwards compatible layer that is beneficial when porting applications.
Connecting to amqp with channel_max value of 0 is no longer allowed.
I bypassed this by setting channel_max to 0 in rabbitmq, but this is not ideal.
The third parameter to amqp_login should be changed
The text was updated successfully, but these errors were encountered: