Category: Apache ActiveMQ®
Blog
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:
Blog
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.
Blog
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.
Blog
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.
Blog
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.
Blog
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.