Chapter 5. Unsupported and Deprecated Functionality

5.1. Unsupported Features

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

The content set forth herein does not constitute a binding agreement or impose any legal obligation on Red Hat. This information is provided for discussion purposes only and is subject to change.

Databases and Database Connectors

The Red Hat JBoss Enterprise Application Platform (EAP) 7 Supported Configurations knowledgebase article on the Red Hat Customer Portal lists databases and database connectors that were tested as part of the JBoss EAP 7.3 release.

Using databases and database connectors that have not been tested as part of the JBoss EAP 7.3 release might cause issues on your JBoss EAP 7.3 instance.

Internal Datasources and Drivers for OpenShift JDK 11 Image

The Red Hat JBoss Enterprise Application Platform (EAP) 7 Supported Configurations knowledgebase article on the Red Hat Customer Portal lists databases and database connectors for the OpenShift JDK 11 image that were tested as part of the JBoss EAP 7.3 release.

For best performance for your JBoss EAP applications, use JDBC drivers obtained from your database vendor.

Additional resources

Eclipse MicroProfile Capabilities

The following Eclipse MicroProfile capabilities that were included as technology preview in JBoss EAP 7.3 CD releases and in the JBoss EAP 7.3 beta release are no longer available:

  • microprofile-smallrye-health
  • microprofile-smallrye-metrics
  • microprofile-smallrye-config
  • microprofile-smallrye-opentracing

We plan to deliver JBoss EAP support of Eclipse MicroProfile APIs in a future release via an expansion mechanism.

5.2. Deprecated Features

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.

5.2.1. Platforms and Features

Support for the following platforms and features is deprecated:

  • Windows Server 2012 R2 and associated IIS web server

  • The use of Red Hat JBoss Operations Network (JON) for managing JBoss EAP is deprecated.

    The use of Red Hat JBoss Operations Network (JON) for managing JBoss EAP was deprecated in the JBoss EAP 7.2 release. With the JBoss EAP 7.3 release, it is still deprecated.

    The latest JON plugin update has received limited testing and bug fixing for JBoss EAP 7.3, in accordance with the limited support provided during the migration support phase of the JON lifecycle. Critical JON fixes for production JBoss EAP and other Red Hat Middleware workloads are provided in this phase of the lifecycle, however the plugins are not updated for new JBoss EAP capabilities. New capabilities may be unavailable through the plugin, or may introduce incompatibilities.

    JON 3.3 requires that users install the JON EAP Management plug-in pack update 11 or newer to be compatible with JBoss EAP 7.3.

Java APIs

  • SAAJ 1.3 was deprecated and SAAJ 1.4 is the default in JBoss EAP 7.3.

    The change in the default SAAJ version may cause issues with user defined SOAP handlers on migrating to JBoss EAP 7.3 from a previous release. To resolve issues arising due to SAAJ version, set the system property -Djboss.saaj.api.version=1.3 to use the deprecated API.

RHEL 6 AMI images

Red Hat Enterprise Linux version 6 AMI images are deprecated. This means that while RHEL 6 AMI images are still included and supported, no enhancements will be made to these features and they may be removed in the future. Red Hat will continue providing full support and bug fixes under our standard support terms and conditions.

Note

Red Hat Enterprise Linux version 6 is currently scheduled to reach its "End of Maintenance Support or Maintenance Support 2 (Product retirement)" phase as of November 30, 2020.

OpenShift Automated Transaction Recovery Capability

The Automated Transaction Recovery capability, which was provided as a technology preview, has been deprecated.

The supported alternative is to use the EAP operator to recover from transactions safely.

Support for the following Automated Transaction Recovery technology preview artifacts has also been deprecated:

  • Transaction recovery application templates

    • eap73-tx-recovery-s2i
    • eap73-openjdk11-tx-recovery-s2i
  • The jta-crash-rec-eap7 quickstart for OpenShift

Additional Resources