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

Using SSL in the JBoss EAP6 cluster


In a clustering environment, applying SSL does not seem as straightforward as in a single-server environment. We have a load balancer and worker nodes in a cluster, so we need to decide in which place we should enable SSL. Here are the two possible places:

  • The communication between users and the load balancer

  • The communication between the load balancer and the worker nodes

In practice, we usually enable SSL between users and the load balancer to secure their communication, and use cleartext communication between the load balancer and the worker nodes. Here is the deployment diagram:

This is reasonable because the worker nodes are usually protected by a firewall, and the purpose of using SSL is not only for encrypting communication channel, but a certificate signed by an authority can also help the customers' web browsers to verify the identity of the web server.

Enabling SSL communication between the load balancer and the worker node also creates many overheads...