Book Image

HornetQ Messaging Developer's Guide

By : Piero Giacomelli
Book Image

HornetQ Messaging Developer's Guide

By: Piero Giacomelli

Overview of this book

<p>Messages and information can be exchanged at exponential speed with JBoss HornetQ asynchronous messaging middleware. Learn how to use the JAVA open source Message Oriented Framework, to build a high-performance, multi-protocol, embeddable, clustered system and manage millions of messages per second.<br /><br />In the HornetQ Messaging Developer’s Guide you will find the most common applications of a message exchanger with example code, as part of real-world scenarios. This practical and applicable guide increases reader knowledge chapter by chapter, covering basics to the most advanced features.<br /><br />You will start from a clean installation of a HornetQ sever and, having progressively become a HornetQ master, will finish by being able to use the framework embedded in your software and sharing information in a cluster environment.<br /><br />Starting from writing and reading a single message, we will discover more advanced features like managing queues, clustering the server, and controlling the undelivered messages. The book deals with a real-world advanced medical scenario as the main example that will lead you from learning the basics to the advanced features of HornetQ.</p>
Table of Contents (18 chapters)
HornetQ Messaging Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

A word on the operating system


HornetQ is nearly operating system agnostic, but as usual, there are some OS-dependent setup procedures that should be considered. HornetQ comes with its own high-performance journaling, and ready-for-persistence purpose libraries. In a Linux environment, starting from kernel 2.6, HornetQ can also benefit from using Linux's Asynchronous IO library (AIO). For our test, we will use two virtual machines created using VirtualBox; one is a 32-bit Windows 2008 Server and the other is an Ubuntu 11.10. So I will explain the differences between the two OSs, but in some cases I will only give the procedure for one OS, referring the reader to where they can check the procedure for the other OS.