Chapter 3. Unsupported functionality 3.1. Unsupported features Support for some technologies are removed due to the high maintenance cost, low community interest, and better alternative solutions. Platforms and features JBoss EAP deprecated the following platforms in version 7.1. These platforms are not tested in JBoss EAP 7.4. Oracle Solaris 10 on x86_64 Oracle Solaris 10 on SPARC64 Oracle Solaris 11 on x86_64 Oracle Solaris 11 on SPARC64 JBoss EAP 7.4 does not include the Wildfly SSL natives for these platforms. As a result, SSL operations in Oracle Solaris platforms might be slower than they were on versions of JBoss EAP. Databases and database connectors IBM DB2 11.1 PostgreSQL/EnterpriseDB 11 MariaDB 10.1 MS SQL 2017 Lightweight Directory Access Protocol (LDAP) servers Red Hat Directory Server 10.0 Red Hat Directory Server 10.1 Keystore defect with Java jdk8u292-b10 If you're running JBoss EAP on Java jdk8u292-b10 and using a legacy security realm or an Elyton Lightweight Directory Access Protocol (LDAP) keystore, you cannot use a Public-Key Cryptography Standards (PKCS) #12 keystore. The workaround is to configure your instance of JBoss EAP to use a stronger default key protection algorithm for PKCS #12 keystores. Other Elytron keystore types are not affected by this defect. RESTEasy parameters RESTEasy provides a Servlet 3.0 ServletContainerInitializer integration interface that performs an automatic scan of resources and providers for a servlet. Containers can use this integration interface to start an application. Therefore, use of the following RESTEasy parameters is no longer supported: resteasy.scan resteasy.scan.providers resteasy.scan.resources MicroProfile capabilities The following MicroProfile capabilities that were included as technical preview in JBoss EAP 7.3 are not included in JBoss EAP 7.4 or in future versions: MicroProfile Config MicroProfile REST client MicroProfile Health JBoss EAP no longer includes the microprofile-smallrye-health subsystem, so application healthiness checks are no longer available. JBoss EAP continues to include healthiness check for the server runtime. MicroProfile Metrics JBoss EAP no longer includes the microprofile-smallrye-metrics subsystem, so application metrics are no longer available. JBoss EAP continues to include endpoints for JVM and server metrics. MicroProfile OpenTracing MicroProfile OpenTracing is now part of the observability decorator layer. These capabilities are now part of the JBoss EAP Expansion Pack (JBoss EAP XP). Install JBoss EAP XP for full MicroProfile support in JBoss EAP. For complete information about support for MicroProfile and JBoss EAP XP, see the JBoss EAP XP lifecycle and support policies page . Red Hat JBoss Operations Network Using Red Hat JBoss Operations Network (JON) for JBoss EAP management is deprecated since JBoss EAP version 7.2. For JBoss EAP 7.4, support for Red Hat JON for JBoss EAP management is deprecated. MS SQL Server 2017 MS SQL Server 2017 is not supported in JBoss EAP 7.4. Microsoft Windows Server 2012 JBoss EAP 7.4 does not support the use of the Microsoft Windows Server 2012 virtual operating system when using JBoss EAP 7.4 in Microsoft Azure. 3.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 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. Platforms and features Support for the following platforms and features is deprecated: Eclipse MicroProfile REST Client API The Eclipse MicroProfile REST Client API is deprecated from the jaxrs subsystem. OpenShift Container Platform 3.11 OpenShift Container Platform (OCP) 3.11 is deprecated for JBoss EAP7.4. Operating systems Microsoft Windows Server on i686 Red Hat Enterprise Linux (RHEL) 6 on i686 Note Although support for these platforms was deprecated in a JBoss EAP release, some artifacts and resources linked to these platforms were not removed, such as the wildfly-openssl native library binding . For Red Hat JBoss Enterprise Application Platform 7.4, those artifacts and resources have been removed. OpenJDK11 OpenShift images support multiple architectures OpenJ9 images for IBM Z and IBM Power Systems will be deprecated. The following OpenJDK11 Builder and Runtime images have been updated to support multiple architectures: jboss-eap-7/eap74-openjdk11-openshift-rhel8 (Builder image) jboss-eap-7/eap74-openjdk11-runtime-openshift-rhel8 (Runtime image) You can use the OpenJDK11 images with the following architectures: x86 (x86_64) s390x (IBM Z) ppc64le (IBM Power Systems) If you want to use the OpenJ9 Java Virtual Machine (JVM) with the OpenJDK11 images, see Java Change in Power and Z OpenShift Images . Spring BOM The following Spring BOM that is located in the Red Hat Maven repository is now deprecated: jboss-eap-jakartaee8-with-spring4 Although Red Hat tests that Spring applications run on Red Hat JBoss Enterprise Application Platform 7.4, you must use the latest version of the Spring Framework and its BOMs (for example, x.y.z.RELEASE ) for developing your applications on JBoss EAP 7.4. For more information about versions of the Spring Framework, see Spring Framework Versions on GitHub . BOMs The existing BOMs are deprecated with a view to providing BOMs (perhaps including some of the existing ones) relevant to the functionality in the major version of JBoss EAP. Java Development Kits (JDKs) JDK 8 JDK 11 NOTE In future JBoss EAP releases, Java SE requirements will be reevaluated based on the industry (for example, Jakarta EE 10+, MicroProfile and so on) and market needs. JBoss EAP OpenShift templates JBoss EAP templates for OpenShift are deprecated. eap74-beta-starter-s2i.json and eap73-third-party-db-s2i.json templates The eap74-beta-starter-s2i.json and eap74-beta-third-party-db-s2i.json templates are deprecated and are removed in JBoss EAP 7.4.0.GA. Legacy security subsystem The org.jboss.as.security extension and the legacy security subsystem it supports are now deprecated. Migrate your security implementations from the security subsystem to the elytron subsystem. PicketLink The org.wildfly.extension.picketlink extension, and the picketlink-federation and picketlink-identity-management subsystems this extension supports, are now deprecated. Migrate your single sign-on implementation to Red Hat Single Sign-On. PicketBox The PicketBox-based security vault, including access by using the legacy security subsystem and the core-service=vault kernel management resources, is now deprecated in this release. Managed domain support for versions of JBoss EAP Support for hosts running JBoss EAP 7.3 and earlier versions in a JBoss EAP 7.4 managed domain is deprecated. Migrate the hosts in your managed domains to JBoss EAP 7.4. Server configuration files using namespaces from JBoss EAP 7.3 and earlier Using server configuration files ( standalone.xml , host.xml , and domain.xml ) that include namespaces from JBoss EAP 7.3 and earlier is deprecated in this release. Update your server configuration files to use JBoss EAP 7.4 namespaces. JBoss EAP Server Side JavaScript support Previously, JBoss EAP Server Side JavaScript support was offered as a Technology Preview. It is now deprecated in this release. Agroal subsystem The datasources-agroal subsystem is deprecated. Codehaus Jackson The Codehaus Jackson 1.x module, which is currently unsupported, is deprecated in JBoss EAP 7.4. application-security-domain resources The application-security-domain resources in ejb3 and undertow subsystems are deprecated. Clustering subsystems The following resources in the clustering subsystems are deprecated: The infinispan subsystem The jgroups subsystem Salted Challenge Response Authentication Mechanism The following Salted Challenge Response Authentication Mechanisms (SCRAMs) and their channel-binding variants are deprecated: SCRAM-SHA-512 SCRAM-SHA-384 Quickstarts The existing Quickstarts are deprecated with a view to providing Quickstarts (perhaps including some of the existing ones), relevant to the functionality in the major version of JBoss EAP. Hibernate ORM 5.1 The Hibernate ORM 5.1 native API bytecode transformer has always been deprecated since it was originally introduced. HornetQ messaging client The HornetQ messaging client is deprecated.

Commands:
/subsystem=infinispan/remote-cache-container=*/component=transaction
/subsystem=infinispan/remote-cache-container=*/near-cache=*
/subsystem=jgroups/stack=*/protocol=S3_PING
/subsystem=jgroups/stack=*/protocol=GOOGLE_PING