Skip to content

Commit e982ff8

Browse files
myfearmyfear
committed
Finish Clustering Demo
1 parent 5c16f1f commit e982ff8

2 files changed

Lines changed: 20 additions & 1 deletion

File tree

‎images/wildfly_cluster4.png‎

149 KB
Loading

‎readme.adoc‎

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -503,10 +503,29 @@ You do already know the command syntax. Beside linking the db, we also link the
503503
.Loadbalancer registered first WildFly instance.
504504
image::images/wildfly_cluster3.png[]
505505

506+
To make sure the Ticket Monster App is also running just visit http://dockerhost/ticket-monster and you will be presented with the ticket monster welcome screen.
506507

508+
.Clustered Ticket Monster Application
509+
image::images/wildfly_cluster4.png[]
507510

511+
You can now start as many wildfly instances you want (and your computer memory can handle):
512+
[source, text]
513+
----
514+
docker run -d --name server2 --link db:db --link modcluster:modcluster <INSTRUCTOR_IP>:5000/ticketmonster-pgsql-wildfly
515+
docker run -d --name server3 --link db:db --link modcluster:modcluster <INSTRUCTOR_IP>:5000/ticketmonster-pgsql-wildfly
516+
docker run -d --name server4 --link db:db --link modcluster:modcluster <INSTRUCTOR_IP>:5000/ticketmonster-pgsql-wildfly
517+
----
518+
519+
You can stop some servers and check the application behavior:
520+
[source, text]
521+
----
522+
docker stop server1
523+
docker stop server3
524+
525+
----
526+
527+
TODO: Pick, which parts we want to describe in more detail from here: https://goldmann.pl/blog/2013/10/07/wildfly-cluster-using-docker-on-fedora/
508528
509-
https://github.com/rafabene/devops-demo
510529
511530
## Test Java EE Applications on Docker
512531

0 commit comments

Comments
 (0)