ActiveMQ-EXPtools is a security utility that detects and exploits multiple Apache ActiveMQ CVEs, provides Perl reverse‑shell payloads for CVE‑2015‑5254, notes authentication requirements for CVE‑2022‑41678, and offers download links and references for further analysis.
The article chronicles the author’s evolution with message queues—from early experiments with ActiveMQ, through Redis and RabbitMQ, to MetaQ and RocketMQ—highlighting real‑world challenges, architectural decisions, scaling tactics, and practical insights for building robust asynchronous systems.
This article introduces five widely used message middleware systems—Kafka, RabbitMQ, ActiveMQ, RocketMQ, and Pulsar—explaining their core architectures, key components, typical use cases, and advantages for building reliable, high‑throughput backend solutions.
This comprehensive article explains the fundamentals of message‑queue middleware, covering point‑to‑point and publish/subscribe models, key evaluation metrics, detailed comparisons of RabbitMQ, Kafka, RocketMQ and ActiveMQ, and deep dives into Kafka and RocketMQ architectures, features, and best‑practice usage.
This article provides a detailed side‑by‑side comparison of five popular message‑queue systems—Kafka, RabbitMQ, ZeroMQ, RocketMQ, and ActiveMQ—covering documentation, programming languages, supported protocols, storage, transactions, load balancing, clustering, management UI, availability, duplication handling, throughput, subscription models, ordering, acknowledgments, replay, retry, concurrency, and includes promotional information from the author.
This article chronicles the author's four‑stage evolution with message queues—from early experiments with ActiveMQ, through Redis and RabbitMQ, to MetaQ and finally RocketMQ—highlighting practical challenges, architectural decisions, performance tuning, and insights for building robust, high‑throughput backend systems.
This comprehensive guide explains the core concepts, deployment modes, evaluation criteria, and detailed pros and cons of the four major message‑queue platforms—Kafka, RabbitMQ, RocketMQ, and ActiveMQ—helping engineers make informed decisions for interview preparation and system design.
This article introduces and compares four widely used open-source distributed message-queue systems—Kafka, ActiveMQ, RabbitMQ, and RocketMQ—detailing their architectures, deployment requirements, features, high-availability solutions, advantages, disadvantages, and provides guidance for selecting the appropriate middleware in large-scale applications.
An in‑depth guide compares the four major message‑queue middleware—Kafka, RabbitMQ, RocketMQ and ActiveMQ—detailing their architectures, modes, evaluation criteria, strengths, weaknesses, and selection considerations to help engineers and interviewees answer critical MQ interview questions and make informed technology choices.
This article introduces the fundamentals of message queues and compares five popular products—ActiveMQ, RabbitMQ, ZeroMQ, Kafka, and RocketMQ—detailing their features, typical use cases, and providing curated learning resources for each.
This article introduces the concepts, core features, deployment environments, architectures, high‑availability solutions, advantages and disadvantages of four widely used open‑source distributed message queue systems—Kafka, ActiveMQ, RabbitMQ, and RocketMQ—and provides a comparative analysis to help practitioners choose the right middleware for their distributed applications.
This article explains why message queues are used in modern systems, outlines common interview questions about MQ, discusses the advantages of decoupling, asynchronous processing, and traffic shaping, examines the pros and cons of MQ, and compares the four major MQ products—Kafka, ActiveMQ, RabbitMQ, and RocketMQ—to help candidates prepare for technical interviews.
This article analyzes why an ActiveMQ notification queue became overloaded during transaction spikes, identifies synchronization and configuration bottlenecks, and presents three practical optimization steps—including removing a synchronized lock, tuning queuePrefetch, and redesigning with dual queues—to dramatically improve throughput.
This article analyzes the causes of data backlog in an ActiveMQ message queue, demonstrates how synchronized locks and default prefetch settings limit throughput, and presents three optimization phases—including removing the lock, adjusting queuePrefetch, and redesigning queue handling—to achieve over 30‑fold performance improvement.
This article provides a detailed side‑by‑side analysis of four major distributed message‑queue systems—Kafka, RabbitMQ, RocketMQ, and ActiveMQ—examining them across seventeen criteria such as documentation, language support, protocols, storage, transactions, load balancing, clustering, management UI, availability, duplication, throughput, subscription models, ordering, acknowledgments, replay, retry, and concurrency.
This article explains why message queues are used, outlines their advantages and disadvantages, compares Kafka, ActiveMQ, RabbitMQ, and RocketMQ in terms of throughput, latency, reliability and features, and provides interview‑style guidance on high availability, idempotency, data loss prevention, ordering, and scaling strategies.
This article compares ActiveMQ, RocketMQ, and Kafka across multiple dimensions such as messaging models, API completeness, language support, throughput, latency, availability, message loss risk, documentation, community activity, and commercial backing, helping readers choose the most suitable queue for their backend needs.
This guide walks through setting up a three‑node Zookeeper ensemble, configuring ActiveMQ with replicated LevelDB storage, and starting the services on each host, providing full command‑line steps, configuration snippets, and verification screenshots for a production‑grade deployment.
This article explains the concept and common use cases of delayed messages and compares five practical implementation methods—using Redis sorted sets, RabbitMQ delayed‑message exchange plugin, ActiveMQ scheduled messages, RocketMQ fixed delay levels, and a custom RocketMQ solution—detailing their workflows, advantages, and drawbacks.
This article explains why message queues are used, their advantages and disadvantages, compares Kafka, ActiveMQ, RabbitMQ, and RocketMQ, and provides interview-focused guidance on high availability, idempotency, reliability, ordering, and handling of message backlog.
This article uses a whimsical group‑chat metaphor to compare four popular message‑queue systems—RabbitMQ, Kafka, RocketMQ and ActiveMQ—explaining their origins, latency, throughput, UI differences, and typical use‑cases such as throttling, decoupling and asynchronous processing.
This article explains the fundamentals of message queues, why they are needed for decoupling, asynchronous processing and throttling, introduces JMS concepts, details ActiveMQ storage options and protocols, and provides practical Java and Spring Boot code examples for producers, consumers, and advanced features such as transactions, persistence, and delayed delivery.
This guide explains how to use Spring Boot's ActiveMQ starter to configure, code, and test both queue (point‑to‑point) and topic (publish‑subscribe) messaging, covering JMS fundamentals, project setup, bean definitions, listener annotations, and dual‑mode container factories.
This article analyzes a severe ActiveMQ message‑queue backlog caused by a synchronized onMessage listener, then demonstrates how removing the lock and tuning the queuePrefetch parameter, along with a dual‑queue redesign, can boost consumption throughput by over thirty times, eliminating the data pile‑up.
This article introduces the fundamentals of message queues, explains their characteristics, delivery models, transmission modes, and push‑pull patterns, then compares four popular implementations—ActiveMQ, RabbitMQ, RocketMQ, and Kafka—highlighting each system's strengths, weaknesses, deployment requirements, and typical use cases.
This article provides a detailed side‑by‑side comparison of five popular message‑queue systems—Kafka, RabbitMQ, ZeroMQ, RocketMQ and ActiveMQ—covering documentation, supported languages, protocols, storage, transactions, load balancing, clustering, management interfaces, availability, throughput, subscription models, ordering, acknowledgments, replay, retry, concurrency and more.
This article provides a comprehensive 17‑point comparison of five popular message queue systems—Kafka, RabbitMQ, ZeroMQ, RocketMQ, and ActiveMQ—covering documentation, supported languages, protocols, storage, transactions, load balancing, clustering, management UI, availability, message duplication, throughput, subscription models, ordering, acknowledgments, replay, retries, concurrency, and more.
This article systematically compares Kafka, RabbitMQ, ZeroMQ, RocketMQ, and ActiveMQ across documentation availability, supported programming languages, protocols, storage models, transaction capabilities, load‑balancing mechanisms, clustering approaches, management interfaces, availability, duplicate handling, throughput, subscription patterns, ordering guarantees, acknowledgment strategies, replay options, retry mechanisms, and concurrency limits, helping engineers choose the right message queue for their needs.
The article explains how delayed message queues replace inefficient scheduled‑task scans in distributed systems, outlines common use cases such as order timeouts and retries, compares RabbitMQ, RocketMQ, Kafka, ActiveMQ and Redis implementations, and details NetEase’s ActiveMQ‑based solution with idempotent processing and traceability.
This article provides a comprehensive 17‑point comparison of five popular message‑queue systems—Kafka, RabbitMQ, ZeroMQ, RocketMQ, and ActiveMQ—covering documentation, language support, protocols, storage, transactions, load balancing, clustering, management UI, availability, duplication guarantees, throughput, subscription models, ordering, acknowledgements, replay, retry mechanisms, and concurrency characteristics.
This article provides a detailed side‑by‑side analysis of five popular message‑queue systems—Kafka, RabbitMQ, ZeroMQ, RocketMQ, and ActiveMQ—covering documentation, programming languages, protocols, storage, transactions, load balancing, clustering, management interfaces, availability, duplication handling, throughput, subscription models, ordering, acknowledgements, backtracking, retry mechanisms, and concurrency characteristics.
This article presents a step‑by‑step migration plan from ActiveMQ to Kafka, covering system dependencies, message type classifications, VirtualTopic usage, and concrete strategies for consumer, producer (1‑1, 1‑N) and self‑consume scenarios to ensure a smooth, zero‑downtime transition.
This article introduces the fundamentals of message middleware, explains its key application scenarios such as asynchronous processing, system decoupling, flow control, and distributed transaction consistency, details the three transmission modes (point‑to‑point, publish/subscribe, request‑reply), and provides a step‑by‑step ActiveMQ quick‑start guide with Spring Boot integration and complete Java code examples.
This article explains the core concepts, component diagram, message flow, cross‑center sequencing, high‑availability design, and detailed ActiveMQ configuration for OneMM message‑oriented middleware, highlighting how asynchronous and decoupled communication improves system efficiency and scalability.
This article provides a comprehensive guide on integrating ActiveMQ with Spring, covering XML configuration of connection factories, producers, consumers, various MessageListener implementations, message conversion, and JMS transaction management, supplemented with complete code examples and deployment instructions.
This article explains how to centralize Java application logs by configuring Log4j's JMSAppender to send log events to an ActiveMQ broker, demonstrates project setup with Maven, shows Spring integration, and provides detailed code examples and troubleshooting steps for reliable remote logging.
This article explains the JMS standard, its two messaging models (Point‑to‑Point and Publish/Subscribe), how messages are consumed synchronously or asynchronously, the core JMS programming objects, and provides an overview of common middleware such as ActiveMQ, RabbitMQ, ZeroMQ, and Kafka.
