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
Connection was closed by remote server: CONNECTION_FORCED #35
Comments
Interesting - have you tried downgrading to see if the errors really goes away with 1.1.7? |
Technically |
No the instance is completely fine and this error only happens on some of the servers (the one that are running amqp storm inside their celery task actually). I will try to downgrade |
Also sometimes i have a different error: AMQPConnectionError: Connection was closed by remote server: CHANNEL_ERROR - expected 'channel.open' |
I'll see if I can reproduce this tonight. Some general questions that could help to narrow this down.
|
Tank you very much for your help. Here is the full code for the logger + socket:
Handler is initialized by parent thread. |
Hello, So i tested using librabbitmq and creating a connection/channel in every subthread but i keep having similar errors so i guess your library is not faulty. Now i think the problem comes from the fact that after a while rabbitmq close the socket if it did not received any message so i am going to try using the heartbeat functionnality. Since i am planning to use amqpstorm, i have a few questions for you in order to better understand how i can use it in my user case. Do you mind responding to them here ?
Thanks for you help and your work on this library. |
I recently moved to a new country so I haven't been able to be as active as I normally would, but I can try to put together a robust example for you in the coming days (or worst case weeks). |
Don't worry, I am starting to get my head around your code and manage to retry on connection loss so all the questions i have are more out of curiosity than to solve my original problem :p For the no_ack=True, where do i set this ? I am not sure it is helpful in my case (i debugged and apparently when pushing on the socket a message with basic.publish, rabbitmq server does not write anything back so that's fine)... PS: Also congratulation on your new position :) Blizzard is it ? That's a really nice company (especially when you are a gamer ahah) |
Sorry, for no_ack=True I was actually confusing it with confirm_deliveries which is actually not set by default. If you call
You could send multiple frames in a single batch, but would require some custom code. Maybe something like this, but I haven't had time to test it yet.
Haha thanks, I have actually been working here for 8 years! I just moved from the French office, to the US office. |
Hello,
We recently updated the library version to 2.1.3 (from 1.1.7) and we now face several errors we did not have previously. One of them is the following:
On the rabbitmq server, we have the following logs:
client unexpectedly closed TCP connection
Finally here is the code i use to create an amqp socket (this socket is then used by logging to send log in the queue) :
Do you have an idea on how to fix these errors ?
The text was updated successfully, but these errors were encountered: