Apache Qpid JMS AMQP 0-8/0-9/0-9-1
		Next

Apache Qpid JMS AMQP 0-8/0-9/0-9-1

Table of Contents

1. Introduction

2. Document Scope And Intended Audience

3. Getting the Client And Dependencies

3.1. Getting the Client
3.2. Dependencies

4. Examples

4.1. Point to point example
4.2. Publish/subscribe example

5. Understanding the Client

5.1. Overview

5.2. ConnectionFactory

5.3. Connection

5.3.1. Failover
5.3.2. Heartbeating
5.3.3. SSL
5.3.4. Message Compression

5.4. Session

5.4.1. Prefetch
5.4.2. TemporaryQueues
5.4.3. CreateQueue
5.4.4. CreateTopic

5.5. MessageProducer

5.5.1. Mandatory Messages
5.5.2. Close When No Route
5.5.3. Immediate Messages
5.5.4. Flow Control

5.6. MessageConsumer

5.6.1. Consumers have Exchange/Queue Declaration and Binding Side Effect
5.6.2. Topic Subscriptions
5.6.3. Maximum Delivery Count

5.7. Destinations

6. JNDI Properties Format

6.1. ConnectionFactory
6.2. Queue
6.3. Topic
6.4. Destination

7. Connection URLs

8. Binding URL

8.1. Binding URL Examples

8.1.1. Binding URLs for declaring of JMS Queues
8.1.2. Binding URLs for declaring of JMS Topics
8.1.3. Wildcard characters in routing keys for topic destinations
8.1.4. More Examples

9. Message Encryption

9.1. Overview

9.2. Sending an Encrypted Message

9.2.1. Providing the Trust Store
9.2.2. Enabling Encryption
9.2.3. Choosing Recipients
9.2.4. Exposing Properties

9.3. Receiving an Encrypted Message

9.3.1. Providing the Key Store

9.4. Message Encryption Example

9.4.1. Introduction
9.4.2. Prerequisites
9.4.3. Broker Configuration
9.4.4. Client Configuration
9.4.5. Application Code

10. System Properties

11. Logging

11.1. Recommended Production Logging Level
11.2. Enabling Debug

A. Exceptions

B. Minimal Maven POM

C. JMS Extensions

C.1. Connection extensions

C.2. ConnectAttemptListener

C.3. Queue Management

C.3.1. Queue creation

C.4. Binding Management

C.4.1. Binding creation

D. PooledConnectionFactory

E. How to bind Qpid destinations and connection factories into Tomcat JNDI

F. Impact of Broker enforced Producer Flow Control on Client

List of Figures

5.1. Architecture of a typical JMS application
5.2. JNDI overview

List of Tables

7.1. Connection URL Options
7.2. Broker List Options
8.1. Binding URL options
8.2. Binding URL examples
10.1. System Properties Affecting Connection Behaviour
10.2. Config Options For Session Behaviour
10.3. Config Options For Consumer Behaviour
10.4. Config Options For Producer Behaviour
10.5. Config Options For Threading
10.6. Config Options For I/O
10.7. Config Options For Security
10.8. Config Options For Security - Standard JVM properties needed when using GSSAPI as the SASL mechanism.
10.9. Config Options For Security - Using SSL for securing connections or using EXTERNAL as the SASL mechanism.
10.10. Config Options For Security - Standard JVM properties needed when Using SSL for securing connections or using EXTERNAL as the SASL mechanism.
A.1. Exceptions linked to JMSExceptions thrown by JMS methods
A.2. Exceptions linked to JMSExceptions received by ExceptionListeners
C.1. Connection Extensions

List of Examples

4.1. JMS Example - Point to Point Messaging
4.2. JMS Example - Point to Point Messaging - JNDI Properties
4.3. JMS Example - Publish/subscribe Messaging
4.4. JMS Example - Publish/subscribe Messaging - JNDI Properties
5.1. Connection URL configured for failover
5.2. Connection URL configured with nofailover
5.3. Connection URL configured for heartbeating
5.4. Connection URL configured for SSL - CA trusted by JVM
5.5. Connection URL configured for SSL - CA not trusted by JVM
5.6. Connection URL configured for SSL - SSL client-auth
5.7. Connection URL configured for SSL - SSL client-auth (2)
7.1. Broker Lists
8.1. Binding URL examples for JMS queues
8.2. Binding URL examples for JMS topics
B.1. Minimal Maven POM
C.1. Inject password extension
C.2. Rotate credentials on authentication failure
C.3. Creation of an LVQ using the Qpid extension to JMS
C.4. Binding a queue using JMS
D.1. Example of configuring PooledConnectionFactory in spring xml configuration.
D.2. Examples of configuring PooledConnectionFactory with DefaultMessageListenerContainer and JmsTemplate.
E.1. An example of Tomcat context.xml declaring Qpid JNDI resources
E.2. An example of JNDI lookup for Qpid resources registered in Tomcat JNDI
E.3. An example of Tomcat context.xml declaring Qpid JNDI resources using deprecated ObjectFactory and deprecated addresses

		Next
		Chapter 1. Introduction

Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners