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
Hello! I have the client which use amqp lib for working with rabbitmq. I have noticed that I can't send any reply until queue has messages. I have checked rabbitmq server and it's alarms, settings and etc. Also rabbitmqctl says that connection in a running state, not blocking. Then I checked basic_publish method in channel.py and notice that every time code can't pass if capabilities.get('connection.blocked', False): checking and think that connection is blocked and makes drain_events instead f send replay. But as I understand it is only capabilities that client can work with blocked connection and can handle it. I can change constant NEGOTIATE_CAPABILITIES and pass their 'connection.blocked': False, but it looks like wrong approach. Is it expected behavior? Could we change it passing any arguments to the client? I have tried to pass argument to the client_properties, but it always rewrites in _on_start method. Because we have constant NEGOTIATE_CAPABILITIES and my server support all of them.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello! I have the client which use amqp lib for working with rabbitmq. I have noticed that I can't send any reply until queue has messages. I have checked rabbitmq server and it's alarms, settings and etc. Also rabbitmqctl says that connection in a running state, not blocking. Then I checked basic_publish method in
channel.py
and notice that every time code can't passif capabilities.get('connection.blocked', False):
checking and think that connection is blocked and makesdrain_events
instead f send replay. But as I understand it is only capabilities that client can work with blocked connection and can handle it. I can change constantNEGOTIATE_CAPABILITIES
and pass their'connection.blocked': False
, but it looks like wrong approach. Is it expected behavior? Could we change it passing any arguments to the client? I have tried to pass argument to the client_properties, but it always rewrites in_on_start
method. Because we have constantNEGOTIATE_CAPABILITIES
and my server support all of them.Beta Was this translation helpful? Give feedback.
All reactions