Replies: 23 comments 4 replies
-
|
@troepolik thank you for reporting the issue. Do you have the same error if you re-consume the same messages?
What do you mean? Can you explain better? ty
What do you mean here? |
Beta Was this translation helpful? Give feedback.
-
|
Can you enable the |
Beta Was this translation helpful? Give feedback.
-
@Gsantomaggio As I understand, error happens inside library and message was skiped, so we dont have possibility to make retry.
We have few queues and they are consumed by few consumers in parallel in one application.
By library. error stack trace is inside library |
Beta Was this translation helpful? Give feedback.
-
@Gsantomaggio thank you! I'l try |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik, I am unable to reproduce the issue.
|
Beta Was this translation helpful? Give feedback.
-
|
Looking at the issue: The buffer seems to be corrupted here. Let's see if the CRC passes before going ahead with the tests |
Beta Was this translation helpful? Give feedback.
-
|
@Gsantomaggio yes, after couple days we've spotted two crc errors, both about the same time: 2025-06-19 02:33:15.530 on rmq server side I see only that warning: this warning was in both of crc error cases. |
Beta Was this translation helpful? Give feedback.
-
|
Repeated and real CRC issues are likely to be a symptom of a more significant underlying problem. Can you please create a simple consumer?, like: var consumerConfiguration = new ConsumerConfig(streamSystem, "<<your_stream>>")
{
OffsetSpec = new OffsetTypeFirst(),
MessageHandler = async (stream, consumerSource, context, message) =>
{
Console.WriteLine($"offset: {context.Offset}, ChunkId:{context.ChunkId}"); Could you see if it is systematic? Run it more than once. |
Beta Was this translation helpful? Give feedback.
-
|
@Gsantomaggio it's not systematic. we have 50rps in this queue and only two errors for 2 days. |
Beta Was this translation helpful? Give feedback.
-
|
Can you confirm that if you read and re-read the exact same stream, with the same program, the CRC error happens just from time to time and you are able to read the messages correctly most of the time? |
Beta Was this translation helpful? Give feedback.
-
|
btw what driver do when crc error happens? will this message be just skipped? |
Beta Was this translation helpful? Give feedback.
-
|
The TCP connection is closed if you enable the CRC and it doesn't match. If you want to skip corrupted chunks, you can disable the CRC check. Is your client remote or in a local network? |
Beta Was this translation helpful? Give feedback.
-
|
@Gsantomaggio @acogoluegnes yes, we've enabled crc. will be "yes, error happens just from time to time, and it was successfully readed next time" |
Beta Was this translation helpful? Give feedback.
-
|
Can you share a simple application that you use to read and re-read and that reproduces the problem? |
Beta Was this translation helpful? Give feedback.
-
I've just connected to stream with the same program with timestamp before error and processed all messages without errors. I will try to prepare simplified program example. |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik, per conversation with the team, we suggest updating to RabbitMQ 4.1. You are using an outdated RabbitMQ version that is no longer supported. There was a bug fixed here: rabbitmq/osiris@0888a21 that could cause your error. Please let us know if the issue occurs again after upgrading to |
Beta Was this translation helpful? Give feedback.
-
|
@Gsantomaggio @acogoluegnes thank you a lot! for your responses and your time! anyway, @acogoluegnes here you can find the example if it still matter. |
Beta Was this translation helpful? Give feedback.
-
I can't reproduce the issue btw |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik this PR #423 adds Crc32 functionalities. |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik do you have news about this issue? We released the new client version with more control for the CRC32 |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik I will close the issue. Let us know how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
@Gsantomaggio good day. Yesterday we've updated server to last rmq version. CRC32 does not match, server crc: 1395186296, local crc: 579286124, Consumer id 0 for stream: xxx, identifier: xxx, reference: xxx, OffsetSpec RabbitMQ.Stream.Client.OffsetTypeOffset Client ProvidedName xxx, No SuperStream, IsSingleActiveConsumer: False, Token IsCancellationRequested: False , Chunk Consumed 1 driver version 1.8.14 |
Beta Was this translation helpful? Give feedback.
-
|
@troepolik may I ask to try the new client version? https://github.com/rabbitmq/rabbitmq-stream-dotnet-client/releases/tag/v1.9.1 the CRC is enabled by default, and try again? Thank you |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
We faced with very rare errors in consuming :
Error | | Error while parsing message Consumer id 0 for stream: xxx, identifier: , reference: xxx, OffsetSpec RabbitMQ.Stream.Client.OffsetTypeOffset Client ProvidedName xxx, No SuperStream, IsSingleActiveConsumer: False, Token IsCancellationRequested: False . The message will be skipped. Please report this issue to the RabbitMQ team on GitHub https://github.com/rabbitmq/rabbitmq-stream-dotnet-client/issuesIssue looks like corrupted internal buffer or mb buffer that used by few threads in the same time.
I dont know if it related or not - we have few parallel consumers, each consumes own queue.
Some times we also have some different type of error, but it also look like corrupted or used by few threads buffer:
We control message body, so I can guarantee that we publish proper json.
We deserialize messages like that:
client version : 1.8.14 - latest
server: RabbitMQ 3.12.0, Erlang 26.2.5
Reproduction steps
Expected behavior
I expect consuming without errors
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions