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
While testing partial partitions, I often find the following function_clause in rabbit_channel:handle_info. It kind of seems like the late answer of a gen_server after a timeout, but instead of be of the form{Ref, LateAnswer} it is {{Ref, Node}, LateAnswer}. In most of the cases, the LateAnswer is {ok, Pid, ok} which could correspond to some of the messages handled in delegate calls, as to rabbit_amqqueue:basic_consume. The second snippet contains an unusal crash in the handle_info, where we get a better trace of this call.
If for any reason a call has timeout but the channel is able to continue working, there should be no harm on ignoring late messages.
While testing partial partitions, I often find the following
function_clause
inrabbit_channel:handle_info
. It kind of seems like the late answer of agen_server
after a timeout, but instead of be of the form{Ref, LateAnswer}
it is{{Ref, Node}, LateAnswer}
. In most of the cases, theLateAnswer
is{ok, Pid, ok}
which could correspond to some of the messages handled in delegate calls, as torabbit_amqqueue:basic_consume
. The second snippet contains an unusal crash in thehandle_info
, where we get a better trace of this call.If for any reason a call has timeout but the channel is able to continue working, there should be no harm on ignoring late messages.
The text was updated successfully, but these errors were encountered: