Category: Devops
Blog
Open Source vs. Commercial Apache ActiveMQ® Support
The finance team sees the "Apache License 2.0" on the ActiveMQ download page and concludes the software is free. The engineering team knows the broker requires configuration, monitoring, tuning, CVE patching, and incident response. All of those things cost engineering time, whether or not a license fee appears on the invoice.
Blog
Apache ActiveMQ® End of Life: What Enterprises Need to Know
If you have searched for Apache ActiveMQ® end of life, you have probably encountered a wall of conflicting answers: some claiming the broker is dead, others insisting it is fine forever. Both are wrong.
Blog
Apache ActiveMQ Zero-Downtime Maintenance: The Complete Procedures Guide
The broker is processing 8,000 messages per second. There are 340 active client connections. A configuration change is needed: a memoryUsage limit increase to prevent an approaching producer flow control event. The question is not whether to make the change. The question is how to make it without dropping messages, disconnecting clients, or triggering a cascade of client reconnect storms that themselves cause the resource pressure you are trying to resolve.
Blog
ActiveMQ Upgrade & Patching Strategy: The Expert Guide
On October 27, 2023, the Apache Software Foundation published CVE-2023-46604, a CVSS 10.0 remote code execution vulnerability in Apache ActiveMQ® that allowed unauthenticated attackers to execute arbitrary code by exploiting the OpenWire protocol's ClassInfo deserialization.
Blog
ActiveMQ Performance Benchmarks: A Complete Methodology Guide
Most ActiveMQ performance benchmarks are wrong, not slightly off, but fundamentally invalid for capacity planning. Performance benchmarking done incorrectly is worse than not benchmarking at all. A number that looks like a throughput measurement but was collected without JVM warmup, without latency percentiles, with the load generator co-located on the broker host, and while producer
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.