What you will learn in ActiveMQ in Action
Chapter by chapter
Chapter 1: Chapter 1. Introduction to Apache ActiveMQ
This introduction positions ActiveMQ as open source messaging middleware for loosely coupled application integration.
What you learn in chapter 1 →Chapter 2: Chapter 2. Understanding message-oriented middleware and JMS
Introduces enterprise messaging, the role of message-oriented middleware, and ActiveMQ’s place in supporting business systems.
What you learn in chapter 2 →Chapter 3: Chapter 3. The ActiveMQ in Action examples
The introduction contrasts the book’s stock portfolio and job queue examples and their respective JMS messaging domains.
What you learn in chapter 3 →Chapter 4: Chapter 4. Connecting to ActiveMQ
Introduces ActiveMQ connectors and their roles in client-to-broker and broker-to-broker communication.
What you learn in chapter 4 →Chapter 5: Chapter 5. ActiveMQ message storage
Introduces JMS delivery persistence, its practical tradeoffs, and ActiveMQ’s storage and in-memory recovery options.
What you learn in chapter 5 →Chapter 6: Chapter 6. Securing ActiveMQ
This introduction explains authentication and authorization in ActiveMQ’s adaptable security model.
What you learn in chapter 6 →Chapter 7: Chapter 7. Creating Java applications with ActiveMQ
This introduction presents an embedded ActiveMQ broker as a way for Java applications to serve both local and remote messaging clients.
What you learn in chapter 7 →Chapter 8: Chapter 8. Integrating ActiveMQ with application servers
This introduction distinguishes Java application-server types and explains the roles of broker creation and JNDI in ActiveMQ integration.
What you learn in chapter 8 →Chapter 9: Chapter 9. ActiveMQ messaging for other languages
The chapter introduction positions ActiveMQ as a cross-platform messaging solution and introduces STOMP’s relevance to scripting languages.
What you learn in chapter 9 →Chapter 10: Chapter 10. Deploying ActiveMQ in the enterprise
This introduction previews enterprise ActiveMQ deployment for high availability, global messaging, and large-scale concurrency.
What you learn in chapter 10 →Chapter 11: Chapter 11. ActiveMQ broker features in action
This introduction outlines advanced ActiveMQ broker features and explains how virtual topics combine topic broadcasts with load-balanced queue dispatch.
What you learn in chapter 11 →Chapter 12: Chapter 12. Advanced client options
The chapter introduction outlines advanced ActiveMQ client features, including exclusive consumers and message groups.
What you learn in chapter 12 →Chapter 13: Chapter 13. Tuning ActiveMQ for performance
This introduction outlines factors affecting ActiveMQ performance and describes two architectural choices that can improve it.
What you learn in chapter 13 →Chapter 14: Chapter 14. Administering and monitoring ActiveMQ
This introduction explains why ActiveMQ brokers need monitoring and administration and identifies JMX as a common management interface.
What you learn in chapter 14 →Concepts explained in this book
- ActiveMQApache ActiveMQ is an open-source message broker that supports JMS and other messaging protocols.
- failover transport connectorAn ActiveMQ transport that automatically reconnects and can connect to another broker when the current broker becomes unavailable.
- ActiveMQ advisory messageAn advisory message is an ActiveMQ message that communicates broker or messaging state to other brokers or clients.
- asynchronous communicationAsynchronous messaging is a communication technique in which a sender transmits a message without waiting for the receiver to respond.
- durable subscriptionA durable subscriber has a subscription that persists and retains messages while the subscriber is disconnected.
- embedded brokerAn embedded broker is a message broker hosted within an application rather than run as a separate service.
- dynamic broker discoveryDynamic broker discovery automatically finds available brokers using mechanisms such as multicast or rendezvous rather than relying on a static list.
- global JNDIGlobal JNDI is a naming configuration scope in which resources are defined centrally and made available to multiple applications.
- local JNDILocal JNDI is a naming configuration scope in which resources are available only to a particular application.
- multicast transportAn ActiveMQ transport that uses multicast to advertise and discover broker services.
- static protocolAn ActiveMQ transport URI scheme that specifies brokers explicitly rather than discovering them dynamically.
- MessageListenerMessageListener.onMessage() is the JMS callback method invoked to deliver a message to an asynchronous consumer.
- discovery protocolAn ActiveMQ client-side transport protocol that discovers available brokers and selects one to connect to.
- network of brokersA network of brokers is a federation in which multiple message brokers are connected to exchange messages.
- network connectorAn ActiveMQ broker component that searches for other brokers and establishes connections between them.
- trust storeA truststore is a repository of certificates that an application trusts when establishing secure communications.
- Jakarta MessagingThe Java Message Service (JMS) is a Java API standard for creating, sending, receiving, and reading messages.
- messaging destinationA JMS destination is an object identifying a location to which messages can be sent or from which they can be received.
- VM transportAn ActiveMQ connector for communicating with a broker embedded in the same application process.
- publish/subscribe modelPublish/subscribe messaging is a messaging style in which publishers send messages to topics for delivery to subscribers.
- JMS connection factoryA JMS connection factory is an object that clients use to create connections to a messaging provider.
- nonpersistent messageNonpersistent delivery mode is a JMS delivery mode that does not require the broker to persist messages to durable storage.
- transport connectorA TCP connector is a broker connector that exposes a client connection endpoint over TCP.
- SSLSSL is a cryptographic protocol for securing communications over a network, superseded by TLS in modern systems.
- SSL transport connectorAn SSL transport connector is an ActiveMQ connector that provides encrypted communication using SSL over TCP.
- remote procedure callA remote procedure call (RPC) is a request-response communication mechanism in which a program invokes an operation provided by another process or system.
- authenticationAuthentication is the process of verifying the identity of a user or system requesting access.
- JMS message headerA JMS message header consists of standard fields that carry metadata about a message.
- point-to-point domainA JMS messaging style in which messages are sent to queues and each message is delivered to one consumer.
- message-oriented middlewareMessage-oriented middleware is software that mediates the exchange of messages and events among distributed applications.
- static network connectorA connector that configures connections between multiple message brokers using a specified list of broker addresses.
- advisorysupportAdvisorySupport is an ActiveMQ class that defines advisory topics and provides helper methods for finding them.
- composite uriA composite URI is a URI whose scheme-specific part contains one or more low-level URIs for establishing connections.
- exponential backoffExponential back-off is a retry strategy in which the delay between attempts increases by a multiplicative factor.
- message cachingBroker-side temporary retention of messages so they remain available to consumers that have disconnected.
- resource adapterThe ActiveMQ resource adapter connects ActiveMQ with a Java EE server through the Java Connector Architecture.
- request-response message exchangeA messaging pattern in which a requester sends a message and receives a corresponding reply.
- JMSDeliveryModeJMSDeliveryMode is a JMS message header indicating whether a message uses persistent or nonpersistent delivery.
- jms providerA JMS provider is an implementation of the JMS interfaces that mediates client interaction with a message-oriented middleware system.
- keepalive protocolA protocol that periodically exchanges lightweight messages and responses to detect whether a transport peer remains reachable.
- rest apiA REST API is an application programming interface that exposes resources through representations and uses HTTP according to REST principles.
- prefetch limitA prefetch limit controls how many messages a broker dispatches to a consumer ahead of acknowledgment.
- AMQ message storeThe AMQ message store is an ActiveMQ storage system that organizes persistent messages, indexes, and related broker data in directories and journal files.
- authorizationAuthorization is the process of determining which actions an authenticated identity is permitted to perform.
- KahaDBKahaDB is the message store used by Apache ActiveMQ for persistent message storage.
- discoveryThe process of detecting remote broker services so clients or brokers can locate available brokers.
- enterprise messagingEnterprise messaging is the exchange of messages among applications in an organizational computing environment.
- RESTREST (Representational State Transfer) is an architectural style for distributed systems that organizes interactions around resources and a uniform interface.
- shared-storage configurationA high-availability broker arrangement in which multiple brokers share a storage mechanism, but only one broker is live at a time.
- vertical scalingVertical scalability is the ability to increase a system's capacity by adding resources to an existing node.
- automatic reconnectionAutomatic reconnection is the behavior of reestablishing a connection after it is interrupted or its broker becomes unavailable.
- message storeA message store is a broker component that holds messages and related delivery state for retrieval and deletion.
- message groupAn ActiveMQ message group routes messages sharing a group identifier to the same consumer, with reassignment if that consumer becomes unavailable.
- JDBC storeA JDBC message store is a message-storage system that persists broker messages in a database accessed through JDBC.
- ActiveMQ CMSCMS (C++ Messaging Service) is a C++ messaging interface that provides functionality similar to JMS.
- exclusive consumerAn ActiveMQ consumer mode in which the broker selects one consumer on a queue to process messages and can select another if the active consumer fails.
- message cacheA message cache is temporary in-memory storage for messages that may be dispatched to active consumers.
- persistent delivery modePersistent delivery mode is a JMS delivery mode that requires the provider to take steps to ensure a message is not lost in transit due to a failure.
- jmx agentA JMX agent is a JVM component that exposes management interfaces and provides agent services and protocol connectors for managing a Java application.
- subscription recovery policyA configurable broker policy that determines which messages are cached for consumers, how many are cached, and for how long.
- JMX MBeanAn MBean is a management bean that exposes an application's resources to external management applications.
- securitySecurity is the protection of a system and its data against unauthorized access, alteration, or disruption.
- shared nothing master/slave configurationA broker deployment in which the master and slave have separate message storage and the slave replicates the master's active state.
- store-and-forward messagingStore-and-forward messaging is a technique in which an intermediary stores messages before forwarding them toward their destinations.
- message-level authorizationAuthorization that determines whether a consumer may access an individual message rather than granting access only when a broker connection is created.
- JMSExpirationJMSExpiration is a JMS message header specifying the time after which a message is considered expired.
- master brokerThe broker in a master/slave arrangement that accepts client activity and whose state is replicated to the slave.
- slave brokerA broker in a master/slave arrangement that waits for the master to fail before taking over shared storage access.
- broker statisticsMeasurements summarizing the operation or state of a message broker or one of its destinations.
- shared database master/slave configurationA broker arrangement in which multiple brokers share a database for message storage, with only one broker accessing it as the active master at a time.
- shared file system master/slave configurationA broker arrangement in which multiple brokers share a file system for message storage, with file locking determining which broker is master.
- ActiveMQ streamAn ActiveMQ feature that transfers data by dividing a stream into JMS messages and reassembling it at the consumer.
- JMS consumerThe example's JMS consumer is a Java program that receives messages from a destination through JMS.
- JMS producerThe example's JMS producer is a Java program that sends messages to a destination through JMS.
- message brokerA message broker is software that routes or mediates messages between messaging clients.
- virtual topicAn ActiveMQ messaging pattern in which publishers send to a topic and consumers receive the resulting messages from queues.
- ActiveMQ JAAS pluginAn ActiveMQ broker plug-in that integrates JAAS login modules for authentication.
- event-driven architectureAn event-driven architecture is a software architecture in which components communicate and coordinate through events.
- asynchronous message consumptionAsynchronous message consumption is a technique in which a provider delivers messages to a consumer without the consumer repeatedly requesting them.
- JMS connectionA JMS connection is a client's connection to a JMS provider, typically represented by an open TCP socket.
- JMS SessionA JMS API context for creating and managing messages, producers, consumers, and destinations.
- synchronous message consumptionSynchronous message consumption is a technique in which a consumer requests a message and waits for the provider's response.
- MessageServletMessageServlet is an ActiveMQ servlet that exposes broker destinations and messaging operations through a web interface.
- BrokerFilterBrokerFilter is an ActiveMQ class that intercepts broker operations and delegates them through a chain of broker filters.
- simple authentication plug-inAn ActiveMQ broker plug-in that authenticates clients using configured credentials.
- message queueA queue is a messaging destination from which consumers receive messages.
- JAAS login moduleA JAAS login module is a component that implements authentication logic within the Java Authentication and Authorization Service framework.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.
