book

Java Message Service

by David A Chappell, Richard Monson-Haefel

December 2000

Intermediate to advanced

240 pages

6h 9m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Java Message Service
A Note Regarding Supplemental Files
Dedication
Preface
What Is the Java Message Service?Who Should Read This Book?OrganizationSoftware and VersionsConventionsComments and QuestionsAcknowledgments
1. Understanding the Messaging Paradigm
1.1. Enterprise Messaging1.1.1. Centralized Architectures1.1.2. Decentralized Architectures1.1.3. Hybrid Architectures1.1.4. Centralized Architecture as a Model1.2. The Java Message Service ( JMS)1.2.1. JMS Messaging Models: Publish-and-Subscribe and Point-to-Point1.2.1.1. Publish-and-subscribe1.2.1.2. Point-to-point1.3. Application Scenarios1.3.1. Enterprise Application Integration1.3.2. Business-to-Business1.3.3. Geographic Dispersion1.3.3.1. One-to-many, push-model applications1.3.4. Building Dynamic Systems with Messaging and JMS1.4. RPC Versus Asynchronous Messaging1.4.1. Tightly Coupled RPC1.4.2. Enterprise Messaging
2. Developing a Simple Example
2.1. The Chat Application2.1.1. Getting Started with the Chat Example2.1.2. Examining the Source Code2.1.2.1. Bootstrapping the JMS client2.1.2.2. Obtaining a JNDI connection2.1.2.3. The TopicConnectionFactory2.1.2.4. The TopicConnection2.1.2.5. The TopicSession2.1.2.6. The Topic2.1.2.7. The TopicPublisher2.1.2.8. The TopicSubscriber2.1.2.9. The Message2.1.3. Sessions and Threading
3. Anatomy of a JMS Message
3.1. Headers3.1.1. Automatically Assigned Headers3.1.1.1. JMSDestination3.1.1.2. JMSDeliveryMode3.1.1.3. JMSMessageID3.1.1.4. JMSTimestamp3.1.1.5. JMSExpiration3.1.1.6. JMSRedelivered3.1.1.7. JMSPriority3.1.2. Developer-Assigned Headers3.1.2.1. JMSReplyTo3.1.2.2. JMSCorrelationID3.1.2.3. JMSType3.2. Properties3.2.1. Application-Specific Properties3.2.2. JMS-Defined Properties3.2.3. Provider-Specific Properties3.3. Message Selectors3.3.1. Message Selector Examples3.4. Message Types3.4.1. Message3.4.2. TextMessage3.4.3. ObjectMessage3.4.4. BytesMessage3.4.5. StreamMessage3.4.6. MapMessage3.4.7. Read-Only Messages3.4.8. Client-Acknowledged Messages3.4.9. Interoperability and Portability of Messages
4. Publish-and-Subscribe Messaging
4.1. Getting Started with the B2B Application4.1.1. Running the B2B Application4.1.2. The B2B Source Code4.1.2.1. The Wholesaler class4.1.2.2. The Retailer class4.2. Temporary Topics4.3. Durable Subscriptions4.4. Publishing the Message Persistently4.4.1. Persistent Messages and Temporary Topics4.5. JMSCorrelationID4.6. Request and Reply4.6.1. TopicSubscriber.receive( )4.6.2. TopicRequestor4.7. Unsubscribing
5. Point-to-Point Messaging
5.1. Point-to-Point and Publish-and-Subscribe5.1.1. When to Use Point-to-Point Messaging5.2. The QWholesaler and QRetailer5.2.1. The QRetailer Class5.2.2. The QWholesaler Class5.3. Creating a Queue Dynamically5.4. Load Balancing Using Multiple QueueSessions5.5. Examining a Queue5.5.1. The QWBrowser Source Code
6. Guaranteed Messaging, Transactions, Acknowledgments, and Failures
6.1. Guaranteed Messaging6.1.1. Message Autonomy6.1.2. Store-and-Forward Messaging6.1.3. Message Acknowledgments and Failure Conditions6.2. Message Acknowledgments6.2.1. AUTO_ACKNOWLEDGE6.2.1.1. The producer’s perspective6.2.1.2. The server’s perspective6.2.1.3. The consumer’s perspective6.2.1.4. Message redelivery6.2.1.5. Point-to-point queues6.2.2. DUPS_OK_ACKNOWLEDGE6.2.3. CLIENT_ACKNOWLEDGE6.2.3.1. Grouping multiple messages6.3. Message Groups and Acknowledgment6.3.1. Handling Redelivery of Messages in an Application6.3.2. Message Groups in QRetailer6.3.2.1. Compensating transactions6.4. Transacted Messages6.4.1. Creating and Using a JMS Transaction6.4.2. The Transacted Retailer Example6.4.3. Distributed Transactions6.5. Lost Connections6.5.1. The Wholesaler Becomes an ExceptionListener6.6. Dead Message Queues

7. Deployment Considerations
7.1. Performance, Scalability, and Reliability7.1.1. Determining Message Throughput Requirements7.1.2. Testing the Real-World Scenario7.1.2.1. Testing with one client7.1.2.2. Send rate versus receive rate7.1.2.3. Determining hardware requirements7.1.2.4. Finding or building a test bed7.1.2.5. Long duration reliability7.1.2.6. Memory leaks7.2. To Multicast or Not to Multicast7.2.1. TCP/IP7.2.2. UDP7.2.3. IP Multicast7.2.4. Messaging Over IP Multicast7.2.4.1. Duplication, ordering, and reliability of messages7.2.4.2. Centralized and decentralized architectures7.2.4.3. Network routers and firewalls7.2.4.4. Some vendors support both centralized and decentralized architectures7.2.5. The Bottom Line7.3. Security7.3.1. Authentication7.3.2. Authorization7.3.3. Secure Communication7.3.4. Firewalls and HTTP Tunneling7.4. Connecting to the Outside World7.5. Bridging to Other Messaging Systems
8. J2EE, EJB, and JMS
8.1. J2EE Overview8.1.1. Enterprise JavaBeans8.1.2. Servlets8.1.3. JavaServer Pages8.2. J2EE: A United Platform8.3. The JMS Resource in J2EE8.4. The New Message-Driven Bean in EJB 2.0
9. JMS Providers
9.1. IBM: MQSeries9.1.1. Version 5.19.1.2. Next Version9.2. Progress: SonicMQ9.2.1. Version 3.09.2.2. Next Version9.3. Fiorano: FioranoMQ9.3.1. FioranoMQ Multicast 4.59.3.2. FioranoMQ Enterprise 4.59.3.3. Next Version9.4. Softwired: iBus9.4.1. iBus//MessageBus 3.19.4.2. iBus//MessageServer 4.19.4.3. iBus//Mobile 1.09.4.4. Next Versions9.5. Sun Microsystems: Java Message Queue9.5.1. Version 1.19.5.2. Next Version9.6. BEA: WebLogic Server9.6.1. Version 5.19.6.2. Next Version9.7. ExoLab: OpenJMS9.7.1. Beta Version 0.49.7.2. Version 1.0
A. The Java Message Service API
A.1. Common FacilitiesA.1.1. BytesMessageA.1.2. ConnectionA.1.3. ConnectionFactoryA.1.4. ConnectionMetaDataA.1.5. DeliveryModeA.1.6. DestinationA.1.7. ExceptionListenerA.1.8. JMSExceptionA.1.9. MapMessageA.1.10. MessageA.1.11. MessageConsumerA.1.12. MessageListenerA.1.13. MessageProducerA.1.14. ObjectMessageA.1.15. SessionA.1.16. StreamMessageA.1.17. TextMessageA.2. Point-to-Point APIA.2.1. QueueA.2.2. QueueBrowserA.2.3. QueueConnectionA.2.4. QueueConnectionFactoryA.2.5. QueueReceiverA.2.6. QueueSenderA.2.7. QueueSessionA.2.8. TemporaryQueueA.3. Publish-and-Subscribe APIA.3.1. TemporaryTopicA.3.2. TopicA.3.3. TopicConnectionA.3.4. TopicConnectionFactoryA.3.5. TopicPublisherA.3.6. TopicSessionA.3.7. TopicSubscriber
B. Message Headers
JMSDestination
JMSDeliveryMode
JMSMessageID
JMSTimestamp
JMSExpiration
JMSRedelivered
JMSPriority
JMSReplyTo
JMSCorrelationID
JMSType
C. Message Properties
C.1. Property NamesC.2. Property ValuesC.3. Read-Only PropertiesC.4. Property Value ConversionC.5. Nonexistent PropertiesC.6. Property IterationC.7. JMS-Defined PropertiesC.7.1. Optional JMS-Defined PropertiesC.7.2. Group JMS-Defined PropertiesC.8. Provider-Specific Properties
D. Message Selectors
D.1. IdentifiersD.2. LiteralsD.3. Comparison OperatorsD.4. Arithmetic OperatorsD.5. Declaring a Message SelectorD.6. Not Delivered Semantics
About the Authors
Colophon
Copyright

Content preview from Java Message Service

Chapter 8. J2EE, EJB, and JMS

J2EE Overview

Java 2, Enterprise Edition ( J2EE) is a specification that unites several other Java enterprise technologies, including JMS, into one complete platform. J2EE is built on three main components: Enterprise JavaBeans, Servlets, and JavaServer Pages ( JSP). Many other technologies, such as JMS, JDBC, JavaMail, JTA, CORBA, and JNDI. are also included as services in J2EE. The Java Message Service actually has two roles in J2EE: it is both a service and the basis for a new enterprise bean type.

To get a better understanding of what J2EE is, and why it is important, we need to discuss the three main components and explain how they are drawn together to form the unified J2EE platform. It is important to keep in mind that all the technologies discussed here are paper specifications licensed and implemented by vendors—a central theme in Sun Microsystems’ enterprise technologies.

Enterprise JavaBeans

Enterprise JavaBeans (EJB) 2.0 defines a Java component model for component transaction monitors (CTMs). A CTM is a marriage of two technologies: distributed objects and transaction processing monitors (TPMs). Distributed object technologies such as CORBA, Java RMI-JRMP, and DCOM provide a networking and routing infrastructure that allows applications to access objects hosted on other processes or computers. A TPM, such as CICS or TUXEDO, provides a robust, secure, and scalable environment for running transactional applications. A CTM combines these technologies ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 0596000685Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design