Category: Apache ActiveMQ®
Blog
ActiveMQ Log Analysis & Diagnostics: The Expert Guide
Senior engineers who are fast at diagnosing ActiveMQ incidents share one trait: they know exactly what they are looking for in the broker log before they open it. They know the PFC signature, the OOM warning pattern, the journal recovery sequence, and the connection drop format. For them, the log is not text to search through, it is a structured operational record that maps each entry to a specific broker state.
Blog
ActiveMQ Capacity Planning: The Complete Framework
Most ActiveMQ deployments are sized in one of two ways: either under-provisioned from underestimating growth ("we'll upgrade when we need to") or over-provisioned from anxiety ("better give it 32GB just in case"). Both approaches are avoidable with a structured capacity planning framework that translates your messaging workload characteristics into specific hardware and configuration requirements.
Blog
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.
Blog
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.
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.