Red Hat JBoss EAP XP 5.0 release notes


Red Hat JBoss Enterprise Application Platform 8.0

For Use with JBoss EAP XP 5.0

Red Hat Customer Content Services

Abstract

This document provides general information about the JBoss EAP XP 5.0 release.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Providing feedback on JBoss EAP documentation

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.

Procedure

  1. Click the following link to create a ticket.
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

Chapter 1. New features and enhancements

1.1. Jakarta EE

Jakarta EE Core Profile

Jakarta EE 10 Core Profile is now available in JBoss EAP XP 5.0.0. The Core Profile is a small, lightweight profile that provides Jakarta EE specifications suitable for smaller runtimes, such as microservices and cloud services. The Jakarta EE 10 Core Profile is available as a Galleon provisioning layer, ee-core-profile-server.

An example configuration file standalone-core-microprofile.xml is provided with JBoss EAP XP 5.0.0 in the EAP_HOME/standalone/configuration directory.

1.2. MicroProfile

MicroProfile Telemetry

The JBoss EAP XP 5.0.0 provides support for MicroProfile Telemetry through the microprofile-telemetry subsystem. This subsystem builds on top of the existing OpenTelemetry subsystem and replaces MicroProfile OpenTracing to provide tracing functionality. For more information, see MicroProfile Telemetry in JBoss EAP and MicroProfile Telemetry administration in Using JBoss EAP XP 5.0.

Configure root directories as ConfigSources

You can now specify a root directory for multiple MicroProfile ConfigSource directories. This means that you do not need to define multiple ConfigSource directories if they share the same parent root directory. For more information, see Configuring root directories as ConfigSources in Using JBoss EAP XP 5.0.

Support for MicroProfile Long Running Action (LRA)

JBoss EAP XP provides MicroProfile Long Running Action (LRA), a standalone MicroProfile specification providing an API for distributed transactions handling based on the saga pattern. This provides a way for transaction handling without the need of taking locks on the data handled in the transaction. For more information, see EAP XP 5 - MicroProfile LRA with Narayana.

Important

MicroProfile Long Running Action is provided as Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.

Support for MicroProfile Reactive Messaging 3.0

JBoss EAP XP 5.0 includes an Advanced Message Queuing Protocol (AMQP) connector with MicroProfile Reactive Messaging. You can use the AMQP connector to connect with AMQ-compliant brokers for asynchronous messaging. For more information, see MicroProfile Reactive Messaging connectors.

Red Hat AMQ Streams

Using Red Hat AMQ Streams with MicroProfile Reactive Messaging on Red Hat OpenShift Container Platform is now fully supported. In the previous release, the support for Red Hat AMQ Streams with MicroProfile Reactive Messaging was technology preview.

1.3. Micrometer

Support for Micrometer subsystem

The JBoss EAP XP 5.0 provides support for Micrometer subsystem and replaces MicroProfile Metrics subsystem. The MeterRegistry of Micrometer is now accessible through CDI, allowing for the inclusion of application metrics with server and JVM metrics. This integration improves monitoring capabilities, providing a solution for tracking system and application performance metrics. For more information, see Micrometer in JBoss EAP and Micrometer administration in Using JBoss EAP XP 5.0.

1.4. Quickstarts

Supported JBoss EAP XP 5.0 quickstarts

All supported JBoss EAP XP 5.0 quickstarts are located at jboss-eap-quickstarts.

The following quickstarts are supported and included with JBoss EAP XP 5.0:

Expand
Quickstart NameDemonstrated TechnologiesDescriptionExperience Level Required

micrometer

Micrometer

The micrometer quickstart demonstrates the use of the Micrometer library in 5.0.

Beginner

microprofile-config

MicroProfile Config

The microprofile-config quickstart demonstrates the use of the MicroProfile Config specification in 5.0.

Beginner

microprofile-fault-tolerance

MicroProfile, Fault Tolerance

The microprofile-fault-tolerance quickstart demonstrates how to use Eclipse MicroProfile Fault Tolerance in 5.0.

Intermediate

microprofile-health

MicroProfile Health

The microprofile-health quickstart demonstrates the use of the MicroProfile Health specification in 5.0.

Beginner

microprofile-jwt

JWT, Security, MicroProfile

The microprofile-jwt quickstart demonstrates the use of the MicroProfile JWT specification in 5.0.

Intermediate

microprofile-lra

MicroProfile LRA

The microprofile-lra quickstart demonstrates the use of the MicroProfile LRA specification in 5.0.

Beginner

microprofile-openapi

MicroProfile OpenAPI

This guide demonstrate how to use the MicroProfile OpenAPI functionality in 5.0 to expose an OpenAPI document for a simple REST application.

Beginner

microprofile-reactive-messaging-kafka

MicroProfile Reactive Messaging

The microprofile-reactive-messaging-kafka quickstart demonstrates the use of the MicroProfile Reactive Messaging specification backed by Apache Kafka in 5.0.

Beginner

microprofile-rest-client

MicroProfile REST Client

The microprofile-rest-client quickstart demonstrates the use of the MicroProfile REST Client specification in 5.0.

Beginner

opentelemetry-tracing

OpenTelemetry Tracing

The opentelemetry-tracing quickstart demonstrates the use of the OpenTelemetry tracing specification in 5.0.

Beginner

The following quickstarts are not supported and not included with JBoss EAP XP 5.0:

microprofile-metrics
microprofile-opentracing
todo-backend

Important

The JBoss EAP XP Quickstarts for Openshift are provided as Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.

Chapter 2. Maintenance support

2.1. Maintenance support for JBoss EAP XP

When a new JBoss EAP XP major version is released, maintenance support for the previous major version begins. Maintenance support usually lasts for 12 weeks.

If you use a JBoss EAP XP major version that is outside of its maintenance support length, you might experience issues as the development of security patches and bug fixes no longer apply. To avoid such issues, upgrade to the newest JBoss EAP XP major version release that is compatible with your JBoss EAP version.

Additional resources

3.1. Unsupported features

Support for some technologies is removed due to the high maintenance cost, low community interest, and better alternative solutions. The following features are not supported in JBoss EAP XP 5.0:

MicroProfile Metrics

MicroProfile Metrics is no longer supported, and is replaced by Micrometer.

MicroProfile OpenTracing

MicroProfile OpenTracing is no longer supported, and is replaced by OpenTelemetry Tracing.

Red Hat OpenShift Streams for Apache Kafka

Since Red Hat no longer offers Red Hat OpenShift Streams for Apache Kafka (RHOSAK), the MicroProfile Reactive Messaging with Kafka quickstart has been updated to not demonstrate connecting to RHOSAK.

Snappy compression disabled for Windows systems

JBoss EAP XP 5.0 does not support Snappy compression on Windows platforms for the MicroProfile Reactive Messaging Kafka connector. The Kafka connector for MicroProfile Reactive Messaging introduced Snappy compression in JBoss EAP XP 4.0.2 using Snappy version 1.1.8.4. However, Java Snappy compression was removed in version 1.1.9.0 of Snappy due to data corruption concerns. JBoss EAP XP 5.0 now uses the latest version of Snappy, 1.1.10.5, which uses native code for compression. The Red Hat build of the Snappy jar includes only the Linux natives.

MicroProfile Reactive Messaging Kafka client

The MicroProfile Reactive Messaging Kafka client available with JBoss EAP XP 5.0 is not supported on Windows platforms.

For a complete list of unsupported features in JBoss EAP 8.0, see the Unsupported features section in JBoss EAP 8.0 Release Notes.

3.2. Deprecated features

Some features have been deprecated with this release. This means that no enhancements are made to these features, and they might be removed in the future, usually the next major release. For more information, see Deprecated features in Red Hat JBoss Enterprise Application Platform expansion pack (EAP XP) 5.

Red Hat continues to provide full support and bug fixes under our standard support terms and conditions. For more information about the Red Hat support policy for JBoss EAP XP, see the Red Hat JBoss Enterprise Application Platform expansion pack life cycle and support policies located on the Red Hat Customer Portal.

Important

All of the features that were deprecated in Red Hat JBoss Enterprise Application Platform 8.0 are also deprecated in JBoss EAP XP 5.0.0. For more information about deprecated features in JBoss EAP 8.0, see Deprecated features in the Release notes for Red Hat JBoss Enterprise Application Platform 8.0.

JBoss EAP OpenShift templates

JBoss EAP templates for OpenShift are removed.

Legacy patching for bootable jar

The legacy patching feature for bootable jar is removed.

Chapter 4. Resolved issues and known issues

4.1. Resolved issues

See Resolved issues for JBoss EAP XP 5.0.0 to view the list of issues that have been resolved for this release.

4.2. Known issues

See Known issues for JBoss EAP XP 5.0.0 to view the list of known issues for this release.

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top