The meshIQ blog.
Our blog offers insights into pivotal and disruptive technologies, including Hybrid Cloud, Messaging Middleware, AI, and more, contributed by meshIQ experts and innovators.
Featured.
AIOps, Messaging, Middleware Optimization, Observability, Streaming
Modernizing Middleware for the AI Era
As AI adoption accelerates, middleware complexity intensifies. In this discussion with meshIQ CEO Navdeep Sidhu, discover why governance—not speed—has become the defining factor for enterprise success, and why fragmented middleware environments can no longer be ignored in the AI era.
Apache ActiveMQ®, Devops, Messaging, Middleware, Middleware Optimization, Monitoring, MQ, Observability, SaaS
ActiveMQ Backup and Disaster Recovery: Complete DR Guide
A message broker’s backup and disaster recovery plan is the last line of defense against scenarios that HA cannot address: a full datacenter outage, catastrophic hardware failure that destroys both primary and secondary nodes, accidental message deletion, or KahaDB corruption that prevents the broker from starting.
Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization, Monitoring, MQ
ActiveMQ JVM Memory & GC Tuning: Heap Sizing, G1GC, ZGC Guide
The JVM is the runtime foundation of every ActiveMQ deployment. Message throughput, delivery latency, producer flow control triggers, OOM crashes, and GC-induced delivery pauses all trace back to JVM memory configuration. Yet ActiveMQ ships with a 512MB heap and no GC logging, appropriate for a developer laptop, not for an enterprise message broker handling millions of messages a day.
Apache ActiveMQ®, Middleware Optimization, Monitoring, Observability
Troubleshooting ActiveMQ Producer Flow Control Blocks
The alert comes in at 2 AM: your order processing service is unresponsive. The application is not crashed, threads are running, the JVM is healthy, but no messages are being sent. Your operations team traces it to a blocked send() call on an ActiveMQ connection. Hours later, after restarting the application, someone finds this line in the broker log from 11 PM the previous day:
Apache ActiveMQ®, Devops, Middleware Optimization, Monitoring
ActiveMQ Protocol Comparison: AMQP vs MQTT vs OpenWire vs STOMP
One of ActiveMQ’s most powerful and underappreciated capabilities is its protocol polyglotism: a single broker can simultaneously accept Java JMS clients over OpenWire, Python services over AMQP, IoT sensors over MQTT, and Ruby scripts over STOMP, all routing messages between each other without protocol bridges or translation middleware.
Apache ActiveMQ®, Apache Kafka®, IBM MQ, Integration, meshIQ, Middleware, Middleware Optimization
The Real Cost of Custom Code: Why Buying a Unified Middleware Management Platform Protects Enterprise IT Budgets
Building custom middleware monitoring appears cost-effective but creates expensive maintenance debt, fragmented visibility, and operational risk. Enterprise teams spend 60-80% of IT budgets on software maintenance while unified platforms deliver immediate, production-ready capabilities.
Apache ActiveMQ®
Apache ActiveMQ 5.19.7 and 6.2.6
On May 27, the Apache ActiveMQ project shipped two releases on the same day: 5.19.7 and 6.2.6. Look at the changelogs side by side and the story is clear — this isn’t a feature drop. It’s a coordinated security-hardening pass applied to both maintained branches of ActiveMQ Classic at once, with the same fixes deliberately backported so that no supported line is left behind.
Apache ActiveMQ®
Upgrading to ActiveMQ 5.19.7 or 6.2.6
The latest Apache ActiveMQ releases – 5.19.7 and 6.2.6, both from May 27 – are good releases to apply. They close known dependency CVEs and tighten the broker’s default posture. (We covered the full list of changes in our release overview.) But here’s the catch with any “secure-by-default” update: hardening defaults means turning things off.
Apache ActiveMQ®, Middleware Optimization, Monitoring
ActiveMQ Message Persistence: KahaDB, Artemis Journal & JDBC
Every persistent message in ActiveMQ must survive a broker restart. That guarantee is the contract behind DeliveryMode.PERSISTENT is what separates a messaging system from a memory buffer. It is also what makes message persistence configuration the most consequential decision in ActiveMQ architecture.
Apache ActiveMQ®, Middleware Optimization
ActiveMQ on Kubernetes: Production Deployment Guide
Kubernetes is now the default deployment substrate for most enterprise platform teams. But ActiveMQ on Kubernetes presents a specific challenge that pure stateless workloads do not: message brokers are stateful.
Apache ActiveMQ®, Middleware Optimization, Monitoring, MQ
ActiveMQ Monitoring & Alerting Setup: The Complete 2026 Guide
Most ActiveMQ outages are not sudden failures. They are visible in the metrics for minutes, sometimes hours, before they become incidents. A memory usage graph climbing past 60%. A queue depth that isn’t draining. An enqueue time that doubled after a deployment. A consumer count that dropped from 3 to 1 at 2 AM.
Apache ActiveMQ®, Middleware Optimization, Monitoring, MQ
ActiveMQ JMS 2.0 Implementation Guide: Simplified API, Transactions & Spring
For most of JMS’s lifetime, writing a simple producer required creating a ConnectionFactory, creating a Connection, starting it, creating a Session, creating a MessageProducer, creating a Message, calling send(), and then closing the producer, session, and connection with the close calls safely wrapped in finally blocks to prevent resource leaks. Every developer knew the pattern. Every developer wrote it slightly differently. Every code review had the same comments about resource management.
Apache ActiveMQ®, Middleware Optimization, Monitoring, MQ
ActiveMQ Security Hardening: TLS, JAAS, LDAP & CVE Patch Guide
In October 2023, security researchers published CVE-2023-46604, a CVSS 10.0 remote code execution vulnerability in Apache ActiveMQ. Within days, it was being actively exploited in ransomware campaigns. The attack required nothing more than network access to port 61616. No authentication, no credentials, no social engineering. The attacker connected to the standard ActiveMQ port and executed arbitrary code on the server.