This project contains several images that allows you to run Ticket Monster on a WildFly server.

The pieces of this demo are:

• Wildfly 10.x Application Server (Standalone mode) + Ticket Monster application - Dockerfile
• Postgres 9.x Database Server - Docker image
• Apache HTTPD + mod_cluster (Using Server advertisement) - Docker image

This is an alternative path for running a "docker only" example using docker-compose.

1. Before start, make sure you have the latest version of the images used on this Demo.

Execute:

  docker-compose pull

2. Start the containers.

Execute:

  docker-compose up -d

3. Check /mcm (mod_cluster manager).

Before starting the Wildfly servers, open /mcm that was exposed on port 80 in the previous step[3]

Execute:

  open http://127.0.0.1/mcm  #For Linux containers
  active=`docker-machine active`; open http://`docker-machine ip $active`/mcm  #For docker-machine containers

Click on Auto Refresh link.

4. Check at /mcm page that Wildfly was registered at modcluster.

5. Scale the Wildfly server.

Execute:

  docker-compose scale wildfly=3

6. Verify that more servers were included at /mcm (mod_cluster manager).

7. Check the logs.

Execute:

  docker-compose logs

8. Access the application.

Execute:

  open http://127.0.0.1/ticket-monster/  #For Linux containers
  active=`docker-machine active`; open http://`docker-machine ip $active`/ticket-monster  #For docker-machine containers

9. Reduce the quantity of servers.

Execute:

  docker-compose scale wildfly=2

10. Stop the cluster.

Execute:

  docker-compose stop
  docker-compose rm