Closed MarcBruins closed 4 years ago
This is because your message does not have the rbs2-msg-id
header.
I don't know how to manually craft messages with Service Bus Explorer, but my guess is that it's possible to provide rbs2-msg-id
manually somehow.
The rbs2-msg-id
header is the minimal requirement for Rebus to attempt to consume a message. Other headers might also be needed, e.g. if you want Rebus' built-in JSON serializer to deserialize the message, you need to provide information about the content. The serializer should throw some helpful exceptions for everything that it needs. 🙂
I hope you'll make it work. 😁
It seems that the required MessageId is not found for my azureservicebus messages. I'm using ServiceBus explorer to create a message which contains a MessageId:
As you can see, the MessageId is there. Now when i start my console app i get the following error:
My configuration looks like this:
Am i forgetting something?
Using version
Rebus.AzureServiceBus 7.1.0
andRebus 6.1.0