rmq | Message queue system written in Go and backed by Redis | Pub Sub library

I am using MassTransit 7.2.2 in a .NET Core application with RabbitMQ(for local development) and SQS(for deployment) where a single message processing can result in multiple new messages getting created and processed.

All the messages share the same base type

Good Day!

I'm trying to implement 2 microservices that communicate with each other through a message broker. But one of them should accept Http requests via REST-Api. Unfortunately, I don't understand how to make the microservice listen to both the message queue and incoming HTTP requests. Perhaps I don’t understand something in the paradigm of communication through a message broker, but how then to receive requests from the client and forward them to the microservice architecture?

Main.ts

So I have an existing web api that uses MediatR commands. I am working on integrating MT into some of them to publish messages to RMQ for various purposes. I am able to integrate it into my commands just fine, but I'm running into issues when testing with the InMemoryHarness during my integration tests.

I have an NUnit Test Fixture that sets up my in memory harness like so, just like the docs describe.

So here is a problem, I am given an integer array, whose number is all distinct, let's say it is

My Nginx configuration files, the same contect with different version, the other one is nginx/1.10.3 takes effect , but current version nginx/1.16.1 error occur, detail as below:

I'm trying to make a fully working example with MassTransit state machine to orchestrate fully decoupled services and running into an exception: The Step1FinishedEvent Event event is not handled during the ProcessingStartedState state for the ArcStateMachine state machine error. During the debug session it seems like the messages (that are consumed by consumers) fire events that are dealt by the state machine too late.

My definitions:

I have a pod running RabbitMQ inside my local cluster. I have configured it like:

So I'm using NestJS (v8) with the RabbitMQ transport (Transport.RMQ) to listen for messages

My NestJS code look something like this:

We have a bunch of pods that use RabbitMQ. If the pods are shut down by K8S with SIGTERM, we have found that our RMQ client (Python Pika) has no time to close the connection to RMQ Server causing it to think those clients are still alive until 2 heartbeats are missed.

Our investigation has turned up that on SIGTERM, K8S kills all in- and most importantly OUTbound TCP connections, among other things (removing endpoints, etc.) Tried to see if any connections were still possible during preStop hooks, but preStop seems very internally focused and no traffic got out.

Has anybody else experienced this issue and solved it? All we need to do is be able to get a message out the door before kubelet slams the door. Our pods are not K8S "Services" so some suggestions didn't help.

Steps to reproduce:

1. add preStop hook sleep 30s to Sender pod
2. tail logs of Receiver pod to see inbound requests
3. enter Sender container's shell & loop curl Receiver - requests appear in the logs
4. k delete pod to start termination of Sender pod
5. curl requests immediately begin to hang in Sender, nothing in the Receiver logs