From the course: Java EE: Application Servers

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Pitfalls of standalone clustering

Pitfalls of standalone clustering

From the course: Java EE: Application Servers

Start my 1-month free trial

Pitfalls of standalone clustering

“

- [Narrator] Clustering in Stand Alone mode can at times present some challenges, especially if you're attempting to cluster on the same machine. To demonstrate from the command line, looking at our Stand Alone installation directory. We're going to copy, the WildFly instance, and call it wildfly dash b. Now, if we do an ls we can see both instances. The issue with starting both of these instances simultaneously is that port conflicts will occur. So, JBoss has designed a way for us to handle this by passing a property at the command line. Or, we could edit the configuration standalone-ha xml, or the standalone.xml, if you just wanted to run two distinct JBoss instances. "ha" by the way, stands for high availability. So, let's focus on the first. We're going to go into our WildFly instance. Bin, standalone, server-config equals standalone-ha xml, and hit enter. Open up a new tab. Going to go into our second WildFly instance. We'll type, let's clear this out so we can see more, type…

Contents