Red Hat JBoss EAP XP 5.0 release notes
For Use with JBoss EAP XP 5.0
Abstract
Making open source more inclusive Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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
- Click the following link to create a ticket.
- Enter a brief description of the issue in the Summary.
- Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
- Clicking Submit creates and routes the issue to the appropriate documentation team.
Chapter 1. New features and enhancements Copy linkLink copied to clipboard!
1.1. Jakarta EE Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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.
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 Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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:
| Quickstart Name | Demonstrated Technologies | Description | Experience Level Required |
|---|---|---|---|
| micrometer | Micrometer |
The | Beginner |
| microprofile-config | MicroProfile Config |
The | Beginner |
| microprofile-fault-tolerance | MicroProfile, Fault Tolerance |
The | Intermediate |
| microprofile-health | MicroProfile Health |
The | Beginner |
| microprofile-jwt | JWT, Security, MicroProfile |
The | Intermediate |
| microprofile-lra | MicroProfile LRA |
The | 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 | Beginner |
| microprofile-rest-client | MicroProfile REST Client |
The | Beginner |
| opentelemetry-tracing | OpenTelemetry Tracing |
The | Beginner |
The following quickstarts are not supported and not included with JBoss EAP XP 5.0:
microprofile-metricsmicroprofile-opentracingtodo-backend
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 Copy linkLink copied to clipboard!
2.1. Maintenance support for JBoss EAP XP Copy linkLink copied to clipboard!
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
- For information about maintenance support, see the Red Hat JBoss Enterprise Application Platform expansion pack (JBoss EAP XP or EAP XP) Life Cycle and Support Policies located on the Red Hat Customer Portal.
Chapter 3. Unsupported features and deprecated features Copy linkLink copied to clipboard!
3.1. Unsupported features Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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.
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 Copy linkLink copied to clipboard!
4.1. Resolved issues Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
See Known issues for JBoss EAP XP 5.0.0 to view the list of known issues for this release.