-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
duplicate header error #1620
Comments
turn out one of our provider produced an invalid message, which already contained cap-msg-group header. Can we move CustomerHeadersBuilder on top of other logic so such cases can be handled by it? |
Each has its own benefits, and placing them on top offers the possibility of rewriting Group. Whether or not to place the |
yes, that is also an option, since other implementations (e.g. Redis) use that approach as well |
Would you want to make a PR? |
sure |
Fixed in v8.3.2 |
Hello, we are getting following exception: An item with the same key has already been added. Key: cap-msg-group
at System.Collections.Generic.Dictionary
2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at DotNetCore.CAP.Kafka.KafkaConsumerClient.Consume(ConsumeResult
2 consumerResult)at DotNetCore.CAP.Kafka.KafkaConsumerClient.Listening(TimeSpan timeout, CancellationToken cancellationToken)
at DotNetCore.CAP.Internal.ConsumerRegister.<>c__DisplayClass21_1.b__2()
This causes consumer to crash, decreases members of kafka consumer and thus increases lag (messages behind). We are not modifying headers and I could not find a message in DB with duplicate cap-msg-group header
any ideas for the cause?
The text was updated successfully, but these errors were encountered: