Closed gastlich closed 6 years ago
I'll try to take a look tonight. I have used cloudamqp in the past for testing.
The issue seems to be that cloudamqp limits the max frame size to 16384 and when amqpstorm tries to forcefully negotiate the max allowed frame size 131072 it silently fails.
I'll implement some logic to better negotiate these things when connecting.
As a temporarily work-around you can change this line to forcefully lower the max frame buffer used by amqpstorm to 16384 and it should work. https://github.com/eandersson/amqpstorm/blob/master/amqpstorm/base.py#L11
@eandersson thank you @eandersson for your help, I will try your suggestion tomorrow
The above pull request should fix any issues with cloudamqp.com. I haven't uploaded it to pypi yet, so you will need to pull it down manually if you want to test it out, but I'll probably ship it in a day or two.
Version 2.4.1 with the patch is now live. Let me know if you have any issues.
@eandersson thanks for the quick release and fixing the issue :) it looks like it's working
@gastlich glad to hear it worked! Let me know if you find any more bugs etc!
Hi there, thanks for a great package and implementing heartbeat timer.
I was developing something locally (pointing to local rabbitmq) and it was working perfectly, but after deploying my app to the cloud and pointing to cloudamqp.com, your package cannot connect anymore...
I've tried to compare your package with other clients:
the last command terminates the terminal.
For you information, our deployment is made to kubernetes on GCP. The connection URL string has a following format:
amqp://user:password@something.something.cloudamqp.com/user
I would appreciate any help :)