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

Testing the server group


Now that we have properly set up the master and slave EAP6, it's time to run them for testing.

Running master

First let's run the following command on master EAP6:

$ ./domain.sh

After the master server starts, let's check the server output shown in the following screenshot:

In the preceding screenshot we can see that master-server has started. Then we can see that the management interface and admin console have also started. The log output is shown in the following screenshot.

Now we can see that the multiple components related with cluster have started:

  • The JGroups subsystem has started.

  • The AJP connector has started. Load balancers will use it for proxy requests. We'll cover this topic in the next chapter.

  • The HTTP connector has started. Because the port offset for master-server is 250 and the HTTP port is bound to 8080, 8080+250 = 8330.

  • mod_cluster has started. We'll learn about mod_cluster in Chapter 5, Load Balancing with mod_cluster.

The described process is shown in...