Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

GlassFish with Automatic Clustering and Scaling

Java EE often looks like a black box when it comes to deployment, clustering and scaling. You can get rid of this complexity using pre-configured clusters in domain mode with automatically scaled instances and standard flows for zero code change deployment. The default topology and scaling triggers can be easily adjusted.

Follow the link to get more details on how clustering works and high availability is configured, as well as how to test this implementation.

GlassFish Cluster Topology

Due to the native GlassFish clustering architecture, its topology includes three node groups:

  • Load Balancer(LB) - intended to process all incoming requests, sent to the cluster, and distribute them between worker nodes
  • Worker Node(W) - application server to handle the required app and web services
  • Domain Administration Server (DAS) - management instance which performs centralized control of the cluster nodes and configure communication between them via SSH

Current implementation of Jelastic scalable GlassFish cluster is built on top of Docker containers. This ensures additional reliability through operating each node as an isolated instance and enables simple container update procedure.

Upon deploying this solution, you’ll get the already configured and ready-to-work GlassFish cluster inside the Cloud, that consists of DAS node, 2 GF application servers (workers), NGINX load balancer and is secured by Jelastic SSL.

For the detailed guidance on this JPS package installation and management, refer to the GlassFish Cluster with Automatic Load Balancing page.

Automatic Scaling and Clustering Configuration

GlassFish cluster package automatically adjusts a number of Worker nodes based on current cluster load (up to 10 instances per layer) according to the following conditions:

  • +1 node if RAM usage > 70% for at least 1 minute
  • -1 node if RAM usage < 40% for at least 10 minute

The appropriate modifications are automatically applied to DAS and Load Balancer configs, and multiple application server instances are automatically interconnected that implements the commonly used clustering configuration.

In case you’d like to change the conditions of automatic nodes’ scaling, refer to the appropriate triggers parameters within the Automatic Horizontal Scaling settings section.

Cloud Hosting Deployment

Public Cloud

To instantly host your own scalable GF cluster, click the GET IT HOSTED button below. Within the opened frame, specify your email address, choose one of the Jelastic Public Cloud providers and press Install.


Private Cloud

If working within Jelastic Private Cloud, copy link of the manifest.jps file above and import it to the required Jelastic installation.