There are notable differences between the JBoss EAP product and the continuous delivery release for JBoss EAP.

Support for Hexadecimal Encoding in JDBC Realm

Elytron now supports hexadecimal encoding for password hashing algorithms in the JDBC realm.

For more information, see Password Mappers in How to Configure Identity Management for JBoss EAP.

Support for Modular Crypt Passwords in JDBC Realm

Modular Crypt password encoding is now supported in the JDBC realm.

The Modular Crypt encoding allows for multiple pieces of information such as the password type, the hash or digest, the salt, and the iteration count to be encoded in a single string.

For more information, see Password Mappers in How to Configure Identity Management for JBoss EAP.

Console access logging

A new feature has been added that outputs access log data to the console. Console access logging data is written to stdout as a single line of JSON-structured data.

For more information, see Configuring a Server in the Configuration Guide book for JBoss EAP.

Ability to Format Syslog Messages

You can now format the message of the syslog payload using the named-formatter attribute.

For more information about using the named-formatter attribute, see Configure Syslog Handler Settings in the Configuration Guide.

Ability to Specify Distributable Session Manager Invocation

You can now specify that a distributable session manager be used when sharing sessions among subdeployments by adding <distributable/> tag under <shared-session-config> in META-INF/jboss-all.xml configuration file.

For more information, see Configuring Session Sharing between Subdeployments in Enterprise Archives in the Development Guide for JBoss EAP.

Ability to Notify Singleton Service Providers of the New Primary Provider

Every member of a cluster with a registered SingletonElectionListener receives a notification when a new primary singleton service provider is elected.

For more information, see HA Singleton Service Election Listener in the Development Guide for JBoss EAP.

The distributable-web subsystem for Distributable Web Session Configurations

The new distributable-web subsystem of JBoss EAP facilitates flexible and distributable web session configurations. The subsystem deprecates the <replication-config> element of jboss-web.xml.

For more information, see The distributable-web subsystem for Distributable Web Session Configurations in the Development Guide and Overiding Default Distributable Session Management Behavior in the Migration Guide for JBoss EAP.

Ability to Store Session Data in a Remote Red Hat Data Grid Cluster

The distributable-web subsystem can be configured to store web session data in a remote Red Hat Data Grid Cluster using the HotRod protocol. Storing web session data in a remote cluster allows the cache layer to scale independently of the application servers.

For information about configuring the distributable-web subsystem, see the Storing Web Session Data In a Remote Red Hat Data Grid in the Development Guide for JBoss EAP.

Configure the Timeout Value for Opening a Message Journal File

You can now configure the timeout value for opening message journal files using the journal-file-open-timeout attribute.

For more information about configuring the journal-file-open-timeout attribute, see Configuring Message Journal Attributes in the Configuring Messaging book for JBoss EAP.

Change in Artemis Logging Codes

Artemis logging codes for Artemis core protocol have changed, whereas the Advanced Message Queuing Protocol (AMQP) codes remain the same. This creates a problem if you are monitoring issues based on these codes.

The logging codes changed because the codes were duplicated between AMQP and the Artemis core protocol.

Omit Prefix on Destination Names

You can configure a connection factory or pooled connection factory to omit the destination name prefix when communicating with a remote Artemis server. Use this option when configuring communication with a remote Artemis 2.x that is not in compatibility mode.

For more information, see Using the Integrated Artemis Resource Adapter for Remote Connections, step 3, or Configuring the Artemis Resource Adapter to Connect to Red Hat AMQ, step 4, in in the Configuring Messaging book for JBoss EAP.

Messaging Enhancements for Load Balancers

In addition to existing support for static HTTP load balancers, load balancers using mod_cluster are now supported. For more information, see Messaging Behind a Load Balancer in the Configuring Messaging book for JBoss EAP.

Messaging to clusters behind load balancers is now fully supported. Clients communicating with clusters behind an HTTP load balancer must re-use the initial connection rather than using the cluster topology. For more information, see Client configuration for messaging behind a load balancer in the Configuring Messaging book for JBoss EAP.

Support for some technologies are removed due to the high maintenance cost, low community interest, and better alternative solutions.

Internal Datasources and Drivers for OpenShift JDK 11 image

The following internal datasources and drivers are no longer provided with the JBoss EAP for OpenShift JDK 11 image:

It is recommended that you use JDBC drivers obtained from your database vendor for your JBoss EAP applications.

For more information about installing drivers, see the Modules, Drivers, and Generic Deployments section in Getting Started with JBoss EAP for OpenShift Container Platform.

For more information on configuring JDBC drivers with JBoss EAP, see the JDBC drivers section in the JBoss EAP Configuration Guide.

Some features have been deprecated with this release. This means that no enhancements will be made to these features, and they may be removed in the future, usually the next major release.

Red Hat will continue providing full support and bug fixes under our standard support terms and conditions. For more information about the Red Hat support policy, see the Red Hat JBoss Middleware Product Update and Support Policy located on the Red Hat Customer Portal.

For details of which features have been deprecated, see the JBoss Enterprise Application Platform Component Details located on the Red Hat Customer Portal.