Chapter 2. Supported Configurations

The only virtual machine operating systems supported for using JBoss EAP in Microsoft Azure are:

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

The Red Hat Cloud Access program allows you to use a JBoss EAP subscription to install JBoss EAP on your own Azure virtual machine or one of the above On-Demand operating systems from the Microsoft Azure Marketplace. Note that virtual machine operating system subscriptions are separate from a JBoss EAP subscription.

Other than the above operating system restrictions, see the Customer Portal for further information on supported configurations for JBoss EAP, such as supported Java Development Kit (JDK) vendors and versions.

2.1. JBoss EAP 7.4 OpenJDK images available in Microsoft Azure

In JBoss EAP 7.4, you can now use OpenJDK 8 images on Red Hat Enterprise Linux 8 virtual machines in Microsoft Azure via Azure Templates.

2.2. Unsupported Features

There are some unsupported features when using JBoss EAP in a Microsoft Azure environment.

ActiveMQ Artemis High Availability Using a Shared Store
JBoss EAP messaging high availability using Artemis shared stores is not supported in Microsoft Azure. To configure JBoss EAP messaging high availability in Azure, see the instructions in the ActiveMQ Artemis High Availability section.
mod_custer Advertising
If you want to use JBoss EAP as an Undertow mod_cluster proxy load balancer, the mod_cluster advertisement functionally is unsupported because of Azure UDP multicast limitations. You must configure mod_cluster load balancing to use a proxy list instead of advertising.
Virtual Machine Scale Set

Transactions in Microsoft Azure Virtual Machine Scale Set (VMSS) is unsupported because the automatic scale down feature does not wait for all transactions to be completed during the scale down process. This could cause data integrity issues. Microsoft Azure VMSS destroys an EAP VM and does not support proper shutdown, which results in the following limitation for EAP clustering:

  • VMSS should be supported for the configurations, in which the server-side state for HA needs to be externalized to a third-party service, such as Red Hat Data Grid. JBoss EAP supports VMSS for HttpSessions externalization, but not for the stateful session bean.
Azure App Service

JTS is not supported in the JBoss EAP Azure App Service offering.

Note

Although JTS is not supported, Jakarta Transactions are supported under the following conditions:

  • The automatic removal of instances is disabled.
  • Instances are not removed manually, for example, by reducing the number of running instances using the Azure dashboard.

Also, transactions over Jakarta Enterprise Beans-remoting are not supported.