I can only add that if I change Request for PublishAsync everything is working and message is being published.
The only time a request client needs to be manually configured is when a specific DestinationAddress or Timeout. Set the Source Queue to Loosel圜ustomerPortalBackenderror and the Destination Queue to Loosel圜ustomerPortalBackend. By default, MassTransit registers a generic request client in the container that publishes requests using the default request parameters. Click Add a new shovel and name it something like Temporary Error Move. T-FAULT rabbitmq://localhost/ml-platform/stops-sagacoordinator:disable-restaurant-state-machine 9f4b0000-f5c9-04d9-21e2-08d99218f114Īt `1.ConfigureTopology(ModelContext context)Īt `1.c_Displa圜lass3_0.-Send>b_0>d.MoveNext()Īt (PipeContext context, Func`2 setupMethod, PayloadFactory`1 payloadFactory)Īt `1.(ModelContext context, IPipe`1 next)Īt .Move(ReceiveContext context, Action`2 preSend)Īt .(ExceptionReceiveContext context, IPipe`1 next)Īt .(ExceptionReceiveContext context, IPipe`1 next)Īt .(ReceiveContext context, IPipe`1 next)Īt (ReceiveContext context, ReceiveLockContext receiveLock)Īt .c_Displa圜lass24_0.b_0>d.MoveNext() MassTransit includes a request client which encapsulates the request/response messaging pattern. Message-based communication is a reliable and scalable way to implement a service oriented architecture. : The channel has been closed.Īt (Func`1 method, CancellationToken cancellationToken)Īt `1.Declare(ModelContext context, Queue queue) My worry is that since SagaStateMachineInstance is ISaga, when I use LoadFrom(context), it scans for all IConsumer and ISaga in the container and for ISaga it calls configurator.Saga(repository), whilst for state machine Sagas we want it to call configurator.StateMachineSaga(machine, repository). MassTransit provides an extensive set of features on top existing message transports, resulting in a developer friendly way to asynchronously connect services using message-based conversation patterns.
I was hoping that a FaultDeclare queue faulted: name: stops-sagacoordinator:disable-restaurant-state-machine_error, durable For example if a message can't be correlated to an existing saga, mass transit throws a sagaexception and puts the message into the error queue. End of stack trace from previous location -Īt `2.SendToOutput(IPipe`1 next, TOutput pipeContext)Īt `1.c_Displa圜lass10_0.g_SendAsync|0>d.MoveNext()Īt .Send(ReceiveContext context, IPipe`1 next)Īt `2.(TContext context, IPipe`1 next) I also did a netstat I see whenever I pump messages, I see a surge on connections opening up at port 5672. Everything works fine till I some limit is hit and I start getting System out memory exceptions and unless I restart my service everything fails. MassTransit.ConnectionException: The connection is stopping and cannot be used: rabbitmq://localhost/Īt (IHostConfiguration hostConfiguration, Func`1 factory, ISupervisor supervisor, CancellationToken cancellationToken)Īt (ConsumeContext`1 context, Exception exception)Īt (ConsumeContext`1 context, TimeSpan duration, String consumerType, Exception exception)Īt .CorrelatedSagaFilter`2.GreenPipes.IFilter>.Send(ConsumeContext`1 context, IPipe`1 next)Īt `1.c_Displa圜lass5_0.g_SendAsync|1>d.MoveNext() Unittesting saga: newly created saga is not under Created property in harness. We are using Saga and for durability we are using nHibernate.