ActiveMQ HTTP transport connector load balanced with HAProxy

If you are using ActiveMQ, you probably use the default tcp transport connector configured in the conf/activemq.xml:

        <transportConnectors>            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>        </transportConnectors>

ActiveMQ also provides other transport connectors for some particular protocols (amqp, mqtt, stomp) or particular transports.

Especially, it supports a very convenient transport connector to go through firewalls: the http transport connector (and extended from http like https, etc.

It means that it’s possible to load balance the HTTP connections. We won’t be able to balance the messages (we need a network of brokers for that, see previous blog posts about that.

However, the HTTP transport is based on the openwire protocol. So, it’s not just a HTTP request to send a message: the client has to send several HTTP requests to establish the connection.

Basically, the client first does a HEAD HTTP request (to get the option of the transport connector, like if the Gzip compression is supported or not), then it sends a series of GET HTTP requests. For each GET request, the ActiveMQ broker will reply the openwire protocol version, the broker topology, etc.

The correlation between each HTTP request is based on a HTTP header: the clientID. The ActiveMQ HTTP connector maintains a map of clients, with their current state, based on the clientID.

If we want to balance the HTTP requests, we can’t use a simple round-robin on each request. Instead we have to balance either:

  1. the client IP address (all requests coming for a IP address will be routed to the same ActiveMQ broker)
  2. the clientID header (all request coming with the same clientID header will be routed to the same ActiveMQ broker)

We are going to use the later (the clientID HTTP header) with HAProxy.

So, imagine, you have two ActiveMQ brokers. Each broker exposes a HTTP transport connector. It means you have the following:

  • amq1 is running on 192.168.134.2, with the HTTP transport connector bound to 8282 for instance
  • amq2 is running on 192.168.134.3, with the HTTP transport connector bound to 8282 for instance

We can “façade” those two ActiveMQ brokers with HAProxy. The HAProxy configuration looks like:

listen balance  bind *:80  mode http  balance hdr(clientID)  server amq1 192.168.134.2:8282  server amq2 192.168.134.3:8282

The important configuration is the balance one, where you can see the use of clientID header for the balancing affinity.

That’s the first post of a series related to ActiveMQ “classic” for the cloud. In the next one, I will show how to use Hazelcast for deal with clientID affinity.

Comments

Post a Comment

Popular posts from this blog

Quarkus and "meta" extension

Quarkus is a great Java framework with a large ecosystem thanks to the extensions . Basically, if using Maven, your pom.xml contains the list of the extensions you want to use, meaning something like this: ... <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-grpc</artifactId> </dependency> <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-opentelemetry</artifactId> </dependency> ... It can quickly become large, and sometime you can have "conflict" between extensions (for example if you mix in the same dependencies set reactive and non reactive extensions). Quarkus "meta" extension To simplify the dependencies for the extensions you want to use (especially if it's basically the same extensions in all your services), you can create your own "meta" extension. This extension doesn't contain actual code, it "wraps" other exten
Read more

Getting started with Apache Karaf Minho

Image
Apache Karaf Minho Apache Karaf Minho is a new runtime, completely created from scratch. The objectives are: super easy to use and run ligtning fast, including GraalVM support Kubernetes compliant to be easily used on the cloud helping to optimize cloud costs by supporting applications colocation providing turnkey services allowing you to create Minho applications in a minute Minho is composed by: minho-boot is the core of Minho. It contains the runtime launcher and the core services (service registry, lifecycle service, configuration service, ...). minho-* services provided additional functionnalities in the runtime. You can use these services to create your own services, it's also where you will find the services managing sepcific kind of applications, allowing colocation. minho-tooling optionally provide convenient tools to create your own runtime. It includes minho-maven-plugin for instance. In this blog post, we will take a quick tour on A
Read more

Apache Karaf Minho and OpenTelemetry

Image
Telemetry is an important part of a software stack, especially on distributed system (where services call each others). OpenTelemetry is a CNCF project coming from OpenTracing and OpenCensus. It provides API to easily instrument your code and tools to collect and export telemetry data (metrics, logs and traces). Before going into how to use OpenTelemetry with Minho, we have to understand some key concepts: Span is a single building block representing an operation or some unit of work that you want to capture. They are capable of standing on their own, referencing (or following) from other spans, storing metadata, tags, etc. Trace is a visualisation of the life of a request (or series of other operations) that is made up of one or more spans. This collection of spans work together to paint a picture of the overall request, allowing you to easily reconstruct what happened within each span, etc. SpanContext is a wrapper of key values pairs that associates a trace to one or mor
Read more