Chapter 4. Unsupported, deprecated, and removed functionality

The following features are not supported by Red Hat.

Logging

JBoss EAP 8.0 does not support Apache Log4j version 1 APIs. If your applications do not package log4j.jar and Log4j configuration as part of the application, then you must update them. For more information about migrating or updating your applications, see the Red Hat Knowledgebase solution Migration: Apache Log4j version 1 is no longer provided in EAP 8.

Agroal subsystem

JBoss EAP 8.0 no longer supports the Agroal subsystem.

Some features are deprecated with this release. This means that no enhancements will be made to these features, and they might be removed in a future release. For more information, see Deprecated in Red Hat JBoss Enterprise Application Platform (EAP) 8.

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.

The following features are deprecated:

JBoss Tools

JBoss Tools is deprecated in JBoss EAP 8.0.

JBoss EAP 8.0 removes the following features.

Jolokia and Prometheus

Jolokia and Prometheus have been removed in this release. These features have been dropped and will no longer be supported by Red Hat. JBoss EAP server exposes metrics through the server metrics endpoint: <server address>:<management port>/metrics.

Environment variables

Red Hat has removed the following environment variables in JBoss EAP 8.0:

JDK 8

JDK 8 has been removed from Red Hat JBoss Enterprise Application Platform 8.0. JDK 11 or JDK 17 is now required.

Legacy security realms

The legacy security realms have been removed from JBoss EAP 8.0. Use the security realms provided in the elytron subsystem instead.

For more information, see the Securing applications and management interfaces using an identity store, and Securing applications and management interfaces using multiple identity stores guides.

Picketbox

PicketBox has been removed from Red Hat JBoss Enterprise Application Platform 8.0. Any legacy security configurations must be migrated to the elytron subsystem. For more information about migrating your security configurations to the elytron subsystem, see Migrating to Elytron.

PicketBox vault

PicketBox vault has been removed from JBoss EAP 8.0. Use the credential store provided by the elytron subsystem to store sensitive strings instead.

For more information, see Credentials and credential stores in Elytron in the Secure storage of credentials in JBoss EAP guide.

PicketLink Subsystem

The PicketLink subsystem has been removed from JBoss EAP 8.0. Use Red Hat build of Keycloak instead of the PicketLink identity provider, and the Galleon layers provided by the Keycloak SAML adapter feature instead of the PicketLink service provider.

For more information, see Securing applications with SAML in the Using single sign-on with JBoss EAP guide.

discovery-group and broadcast-group resources

Red Hat JBoss Enterprise Application Platform 7.4 removed the discovery-group and broadcast-group resources. These resources are still removed in JBoss EAP8.0.

Additionally, Red Hat JBoss Enterprise Application Platform 7.4 reduced the impact to its web console by replacing all instances of discovery-group and broadcast-group resources with jgroups-discovery-group and socket-discovery-group resources.

JBoss EAP 7.3 deprecated the following resources in the messaging subsystem:

JBoss EAP 7.3 replaced these deprecated resources with jgroups-discovery-group and socket-discovery-group resources. Each deprecated resource included an attribute from each replacement resource, with one attribute set to null and the other attribute set to a value greater than 0. These settings caused both discovery-group and broadcast-group to remain active, but still assign all their functionality to the jgroups-discovery-group and socket-discovery-group resources.

Quickstarts

The following outdated or redundant quickstarts have been removed from JBoss EAP 8.0:

Red Hat build of Keycloak Client Adapter

Red Hat JBoss Enterprise Application Platform 8.0 does not provide the Red Hat build of Keycloak Client Adapter. Use the new elytron-oidc-client subsystem to secure applications deployed to JBoss EAP with OpenID Connect (OIDC).

Java service on Red Hat Enterprise Linux

Java service (JSVC) running on Red Hat Enterprise Linux (RHEL) has been removed from JBoss EAP 8.0.

BOMs

The following BOMs have been removed:

For more information, see Migrate a JBoss EAP Application’s Maven Project to JBoss EAP 8.0 in the Migration Guide.

Connector attribute

In JBoss EAP 7.4, the modcluster subsystem deprecates the connector attribute on the proxy element and replaces it with the listener attribute to avoid confusion. The management schema in JBoss EAP 7.4 uses the listener attribute, but also allows setting the connector attribute. In JBoss EAP 8.0, the deprecated connector attribute is removed, and you must now use the listener attribute instead. For more information, see Deprecated in Red Hat JBoss Enterprise Application Platform (EAP) 7.

Changes to the iiop-openjdk subsystem

In JBoss EAP 8.0, the legacy security subsystem has been removed and replaced by the elytron subsystem. You can install the elytron subsystem as the security interceptor for Object resource broker (ORB).

To maintain interoperability with JBoss EAP 7 , for example when running JBoss EAP as a managed domain with a JBoss EAP 8.0 host controller managing a JBoss EAP 7 secondary host controller, the ability to configure legacy security interceptors has been retained.

However, when running JBoss EAP as a standalone server, setting the values client and identity, for iiop-openjdk/security attribute is not supported.

Hibernate Search 5 APIs

Hibernate Search 5 APIs were deprecated in JBoss EAP 7.4 and have been removed in JBoss EAP 8.0 and replaced with Hibernate Search 6 APIs.

To view a list of the removed APIs, see Hibernate Search 5 APIs Deprecated in JBoss EAP 7.4 and removed in EAP 8.0.

Apache Log4j version 1

JBoss EAP 8.0 does not support Apache Log4j version 1 APIs. If your applications do not package log4j.jar and Log4j configuration as part of the application, then you must update these packages. For more information about migrating or updating your applications, see the Red Hat Knowledgebase solution Migration: Apache Log4j version 1 is no longer provided in EAP 8.

For more information, see Removal of Apache Log4j version 1 APIs.

Apache Xerces and Apache Xalan

The Apache Xerces and Apache Xalan JBoss Modules, implementing JAXP version 1.5, have been removed from JBoss EAP 8.0. Use the default JAXP implementation provided by the java.xml JPMS module of JDK instead, which implements JAXP version 1.6. For more information, see Use JAXP implementation provided by the JDK in JBoss EAP.