![]() It healed only after restart of the host. Hope this will help you to find the issue.Īfter this has happend, some receive endpoints failed so hard that Masstransit stopped receiving any messages (only for those failed endpoints). ![]() After digging around in Masstransit sources, looks like the problem could be in PrepareQueueClientFilter in this line of code:Ĭontext.GetOrAddPayload(() => clientContext) Īfter retry attempt, context stays the same and contains old clientContext (with QueueClient), so GetOrAddPayload does nothing. Somehow, when receive logic is retried, the OnMessageAsync method is called several times on the same QueueClient object. This one (see stacktrace) looks like a bug in Masstransit. I am concerned if Masstransit can self-heal after those exceptions properly. It would be great if you could confirm\comment on my assumptions. Staff plan to break ground and begin working on the Alameda
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |