GreenPipes | asynchronous pipe implementation for the Task Parallel | Architecture library

I have following code which create and IRequestClient client and send request and waiting for the response. here you can see, I have set some headers value as well with GreenPipes

When using the request/response pattern, during the deserialization of the response, an incompatibility error occurs. Apparently, the publisher serializer configuration is causing this issue, although the message is as expected.

Using the JsonProperty feature could isolate the problem, however, it does not reflect what was expected.

Versions .NET: 6.0; MassTRansit: 7.3.0; Newtonsoft: 13.0.1

I want to be able to send message from a unit test to an ASP.Net Core application using the in-memory implementation of MassTransit. The in-memory implementation is important as the actual application uses ActiveMQ but we want to replace that during testing with the in-memory implementation.

I started creating a new ASP.Net Core API project from VS2019 using .NET 5 and added MassTransit to Startup as follows:

I'm trying to set MassTransit up with Azure Service Bus. I want to use the DLQ instead of relying on _skipped and _error queues, but I'm not sure if I'm doing it wrong.

This is a simplified version of my setup:

So one in a hundred (Mediator)messages does not get consumed and I can't figure out why. Messages sent via rabbitMq are fine.

Exception:

I am trying to connect two services using RabbitMQ queue. First services pushes value to queue, second retrieves it and process. All is fine, but when second service tries to process job, it throws exception. Queue item stays in JobAttempt queue without any information, and consumer service retries to process job, but throws same exception every time.

Exception

I'm using MassTransit.Kafka for produce and consume messages in batches. When I try to consume message one by one everything works fine, but when I try to consume messages in batches I get an error:

I try to use MassTransit SQS to publish a message. Here is my configuration code:

I use MassTransit SQS. I found out, when publishing a message, this problem occurs:

User is not authorized to perform: SNS:CreateTopic on resource

So I need rights to create topics.

I solved it by asking the admin to extend rights. This works and topics can be created. However, it seems that the topic names are automatically generated based on the class names. Can I modify this behaviour programmatically (so by giving a self described topic name).

This can be useful for creating a FIFO topic (which needs to have a name ending with .fifo).

Update

I am now familiar with formatting (thanks for telling me Chris) with SetEntityName.

But my problem seems to be really fifo specific.

This works: