Chapter 5. Unsupported, deprecated, and removed functionality
5.1. Unsupported features
The following features are not supported by Red Hat.
EAP operator
Red Hat JBoss Enterprise Application Platform 8.0 Beta does not support the EAP operator. You cannot deploy your JBoss EAP applications using the EAP operator. For more information, see JBoss EAP Operator Support Policy.
Logging
JBoss EAP 8.0 Beta 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.
5.2. Deprecated features
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.
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.
Support for the following platforms and features is deprecated:
JDK 11
Support for JDK 11 was deprecated in JBoss EAP 7.4, and JDK 11 continues to be deprecated in JBoss EAP 8.0 Beta. JBoss EAP 8.0 Beta continues to support JDK 17.
Security manager
The Java Security Manager is deprecated.
5.3. Removed features
Version 8.0 Beta removes the following features from JBoss EAP.
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 Beta:
-
GALLEON_PROVISION_DEFAULT_FAT_SERVER
-
AB_JOLOKIA_AUTH_OPENSHIFT
-
AB_JOLOKIA_CONFIG
-
AB_JOLOKIA_DISCOVERY_ENABLED
-
AB_JOLOKIA_HOST
-
AB_JOLOKIA_HTTPS
-
AB_JOLOKIA_ID
-
AB_JOLOKIA_OFF
-
AB_JOLOKIA_OPTS
-
AB_JOLOKIA_PASSWORD
-
AB_JOLOKIA_PASSWORD_RANDOM
-
AB_JOLOKIA_PORT
-
AB_JOLOKIA_USER
-
AB_PROMETHEUS_ENABLE
-
AB_PROMETHEUS_JMX_EXPORTER_CONFIG
-
AB_PROMETHEUS_JMX_EXPORTER_PORT
-
JGROUPS_ENCRYPT_SECRET
JDK 8
JDK 8 has been removed from Red Hat JBoss Enterprise Application Platform 8.0 Beta. JDK 11 or JDK 17 is now required.
Legacy security realms
The legacy security realms have been removed from JBoss EAP 8.0 Beta. 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 Beta. 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 Beta. 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
Using Red Hat Single Sign-On SAML adapters with JBoss EAP 8.0 will be supported when the adapters are released as a .zip
file by Red Hat Single Sign-On.
The PicketLink subsystem has been removed from JBoss EAP 8.0 Beta. Use Red Hat Single Sign-On instead of the PicketLink identity provider, and the Red Hat Single Sign-On SAML adapter instead of the PicketLink service provider.
For more information, see the following resources:
- Using Red Hat Single Sign-On - Red Hat Single Sign-On product page.
- Using the Red Hat Single Sign-On SAML adapter with JBoss EAP - JBoss EAP adapter in the Securing Applications and Services 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 Beta.
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:
-
/subsystem=messaging-activemq/discovery-group=*
-
/subsystem=messaging-activemq/server=default/broadcast-group=*
-
/subsystem=messaging-activemq/server=default/discovery-group=*
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 Beta:
-
app-client
-
bean-validation
-
ejb-asynchronous
-
ejb-in-ear
-
ejb-in-war
-
ejb-security
-
ejb-security-jaas
-
greeter
-
helloworld-html5
-
helloworld-mbean
-
helloworld-mdb-propertysubstitution
-
helloworld-rs
-
helloworld-ssl
-
inter-app
-
jaxws-addressing
-
jaxws-pojo
-
jts-distributed-crash-rec
-
kitchensink-angularjs
-
kitchensink-ear
-
kitchensink-jsp
-
kitchensink-ml
-
logging-tools
-
managed-executor-service
-
messaging-clustering
-
payment-cdi-event
-
resteasy-jaxrs-client
-
spring-greeter
-
spring-kitchensink-basic
-
spring-kitchensink-springmvctest
-
tasks-rs
-
websocket-client
-
xml-jaxp
Red Hat Single Sign-On Client Adapter
Red Hat JBoss Enterprise Application Platform 8.0 Beta does not provide the Red Hat Single Sign-On 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 Beta.
BOMs
The following BOMs have been removed:
-
The
JBoss Jakarta EE 8 Specification APIs
BOM is removed. Use theJBoss EAP EE
BOM in your Maven project. -
The
EAP Runtime Artifacts
BOM is removed. Use theJBoss EAP EE
BOM in your Maven project.
For more information, see changes relating to JBoss EAP 8 BOM updates.