Book Image

JBoss EAP6 High Availability

By : Weinan Li
Book Image

JBoss EAP6 High Availability

By: Weinan Li

Overview of this book

High availability is a system design approach and associated service implementation which ensures that a prearranged level of operational performance will be met during a contractual measurement period. High availability is usually a system combined with many different components that achieve different goals. High availability cluster implementations attempt to build redundancy into a cluster to eliminate single points of failure. JBoss EAP6 High Availability is the perfect guide for learning how to apply the newest technologies provided by JBoss to build your high availability system. With a clear explanation of the design of JBoss EAP6 and its clustering components, this book will help you customize each component to fulfill your specific requirements. Throughout the course of this book, you will learn how to build high availability clusters using the projects provided by JBoss. The book begins with an introduction to the design of JBoss EAP6 and its uses. The next step will be to explore the two companion open source projects - mod_jk and mod_cluster. In this section, you will get to grips with the concept of load balancing with mod_jk and mod_cluster. You will also learn how to enable SSL in the clustering environment and how to configure session replication between EAP6 servers. Furthermore, the appendix section introduces you to some troubleshooting techniques for Wildfly.
Table of Contents (15 chapters)
JBoss EAP6 High Availability
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Configuring mod_cluster


After installing the necessary mod_cluster components in httpd, we will configure them properly in this section.

Configuring httpd.conf

Before we start to configure mod_cluster, we need to do some preparations in httpd.conf. The first thing to do is to change the Listen directive from Listen 80 to the following:

Listen 10.0.1.33:80
Listen 10.0.1.33:6666
Listen 172.16.123.1:80

As we know, lb has two IP addresses: one is the public address 172.16.123.1, and the other is 10.0.1.33, which is the internal IP address of the load balancer used to communicate with the two EAP6 servers. Now let's learn the purpose of the configuration:

  • 10.0.1.33:80 will be used for a mod_cluster management console. We don't want public access of this management console, so we just bind it to the local IP address.

  • 10.0.1.33:6666 will be used by mod_manager to communicate with the EAP6 servers, and the message encapsulated in the MCPM protocol will be transferred through this channel.

  • 172.16.123...