masstransit

问题 I'm trying to build a Kafka consumer using MassTransit I have this piece of code var services = new ServiceCollection(); services.AddMassTransit(x => { x.AddRider(rider => { rider.AddProducer<string, Request>("request", m => m.Message.RequestId); rider.UsingKafka((context, k) => { k.Host("localhost:9092"); }); }); }); var provider = services.BuildServiceProvider(); var producer = provider.GetRequiredService<ITopicProducer<Request>>(); await producer.Produce(new Request() { RequestId = "abc123

问题 I'm having an issue with getting the same instance of the IIdentityService(my own class) or IServiceProvider in my consumer observer. I have an identity service where I set the credentials for the user, which is used later in the consumer pipeline. I have tried the code below along with other code and configuration changes. _serviceProvider.GetRequiredService<IIdentityService>() _serviceProvider.CreateScope() var consumerScopeProvider = _serviceProvider.GetRequiredService

问题 I have a queue {QueueName}. I defined a consumer and faulted-messages consumer as follows: cfg.ReceiveEndpoint ( queueName: QueueName, e => { e.UseMessageRetry(r => r.Immediate(2)); e.AutoDelete = false; e.Durable = true; e.Consumer(() => container.Resolve<My_Consumer>()); e.Consumer(() => container.Resolve<My_Fault_Consumer>()); } ); When consumer dries out its attempts number to handle the message, the faulted-message-consumer kicks in and handles the message by logging the error. I've

问题 I have a queue {QueueName}. I defined a consumer and faulted-messages consumer as follows: cfg.ReceiveEndpoint ( queueName: QueueName, e => { e.UseMessageRetry(r => r.Immediate(2)); e.AutoDelete = false; e.Durable = true; e.Consumer(() => container.Resolve<My_Consumer>()); e.Consumer(() => container.Resolve<My_Fault_Consumer>()); } ); When consumer dries out its attempts number to handle the message, the faulted-message-consumer kicks in and handles the message by logging the error. I've

问题 I have several Asp.Net Core Web APIs that use Bearer authentication and IdentityServer4.AccessTokenValidation middleware to introspect tokens, authenticate the user and create claims. This works fine for HTTP requests. I am in the process of configuring these APIs to also be MassTransit endpoints (for both Publishing and Consuming messages) using RabbitMQ as transport. I followed the instructions here for adding MassTransit to the API and for setting up message consumers. A typical workflow

问题 I have several Asp.Net Core Web APIs that use Bearer authentication and IdentityServer4.AccessTokenValidation middleware to introspect tokens, authenticate the user and create claims. This works fine for HTTP requests. I am in the process of configuring these APIs to also be MassTransit endpoints (for both Publishing and Consuming messages) using RabbitMQ as transport. I followed the instructions here for adding MassTransit to the API and for setting up message consumers. A typical workflow

问题 If I have to much activities, does it cause blocking resources or request time out? Here is my scenario: I have an api controller which sends an Order request to consumer; I use Request/Response patern to recieve ErrorMessage property from consumer and base on that property response back, if it's null I would want to return OK() otherwise, return BadRequest or Ok but with a message like: Product out of stock to notify to the client . In my consumer, I have build a routing slip which have 2

问题 is there a way to support a scenario where broker is offline so that messages can be stored temporarily in disc and attempt to submit once the broker comes online. This is to provide resilience in scenarios where the broker goes down. I have not found anything in the documentation yet. 回答1: There isn't anything like this built into MassTransit. If the broker is unavailable, messages cannot be published or sent. 来源： https://stackoverflow.com/questions/63492266/is-there-a-way-to-persist

问题 Is there a way to specify timeout value when publishing messages using the MassTransit Library. How to handle scenarios when message broker goes down. Now it seems that Publish call waits indefinitely. It would be nice to control these behavior. Should we rely on cancellation token? Timeout implementation might be better. 回答1: You can pass a CancellationToken to Publish . If canceled, an OperationCanceledException will be thrown. If you want to use a timeout, you can create a

问题 Is there a way to specify timeout value when publishing messages using the MassTransit Library. How to handle scenarios when message broker goes down. Now it seems that Publish call waits indefinitely. It would be nice to control these behavior. Should we rely on cancellation token? Timeout implementation might be better. 回答1: You can pass a CancellationToken to Publish . If canceled, an OperationCanceledException will be thrown. If you want to use a timeout, you can create a