JBoss Enterprise Application Platform 7.4 Update 17 Release Notes
In order to better meet customer expectations, micro releases for JBoss EAP 7 have been discontinued and replaced with updates delivered on a repeating schedule.
Each new update will contain a number of bug fixes for customer reported issues and potentially a number of security fixes. We expect that the updates will substantially reduce the number of individual patches that we produce and that customers must manage to keep their installations up to date.
For more information see the following Red Hat Knowledgebase articles: Maintenance Release Changes in EAP 6.2+ and Updated Patch Management with EAP 6.2+
This update includes all fixes and changes from JBoss Enterprise Application Platform 7.4 Update 16
Download This content is not included.JBoss Enterprise Application Platform 7.4 Update 17
This update includes fixes for the following security related issues:
| ID | Component | Impact | Summary |
|---|---|---|---|
| CVE-2024-1233 | Security | Moderate | eap: JBoss EAP: wildfly-elytron has a SSRF security issue |
| CVE-2024-28752 | Web Services | Important | cxf-core: Apache CXF SSRF Vulnerability using the Aegis databinding |
| CVE-2021-23445 | Server | Moderate | datatables.net: contents of array not escaped by HTML escape entities function |
This update includes the following bug fixes or changes:
| ID | Component | Summary |
|---|---|---|
| This content is not included.JBEAP-26389 | EJB | This content is not included.EJBCLIENT-531 - Discovery: take static blocklist into account during cluster discovery |
| This content is not included.JBEAP-26684 | EJB | WFDISC-54 - EJB discovery: when LDAP dir-context is used in cluster only deployments from one node are being discovered |
| This content is not included.JBEAP-26825 | JCA | war containing JDBC drivers deploys an extra driver |
| This content is not included.JBEAP-26003 | JSF | Disable counter-productive "distributable" behavior in Mojarra [details] |
| This content is not included.JBEAP-26824 | JSF | JSF token generation hangs EAP 7.4 Update 15 start up in low entropy environments [details] |
| This content is not included.JBEAP-26688 | JSF | mojarra #4260 - java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 still occurs |
| This content is not included.JBEAP-26363 | Transactions | This content is not included.WFTC-141 - Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false. |
| This content is not included.JBEAP-26686 | Transactions | This content is not included.WFTC-142 - Lower logging level to debug for transaction timeout |
| This content is not included.JBEAP-22656 | Transactions | This content is not included.WFLY-15609 - There is no cleanup of thread bound transaction timeout override on threads used to run servlets [details] |
| This content is not included.JBEAP-26774 | Undertow | This content is not included.UNDERTOW-2347 - Undertow client must send either http/1.1 or both http/1.1 and h2 in SSL ClientHello handshake message |
| This content is not included.JBEAP-26971 | Undertow | This content is not included.UNDERTOW-2351 - NullPointerException on flawed WebSockets war deployment |
| This content is not included.JBEAP-26972 | Undertow | This content is not included.UNDERTOW-2374 - At Http2ReceiveListener.checkRequestHeaders do not check path chars when unescaped characters are allowed |
| This content is not included.JBEAP-26463 | Web Console | This content is not included.HAL-1970 - Exception when viewing datasources in Management Console |
| This content is not included.JBEAP-26756 | Web Sockets | This content is not included.UNDERTOW-2354 - Bootstrap$WebSocketListener.contextDestroyed throws NPE after application start up error [details] |
Installation
Archive / zip / installer based installations
Note: This update zip should only be applied to installer or zip-based installations.
To apply this update using the CLI on Unix-based systems, run the following command from JBOSS_HOME:
bin/jboss-cli.sh "patch apply path/to/jboss-eap-7.4.17-patch.zip"
To apply this update using the CLI on Windows-based systems, run the following command from JBOSS_HOME:
bin\jboss-cli.bat "patch apply path\to\jboss-eap-7.4.17-patch.zip"
These commands will apply the update to the installation that contains the CLI script. Other scenarios and use of the management console are covered in the JBoss EAP 7.4 Patching And Upgrading Guide
RPM installations
See the documentation: Updating an RPM installation
OpenShift Container installations
Update the containers to use the This content is not included.latest tag, to be current on JBoss EAP bug fixes as well as OpenJDK and RHEL fixes.
This content is not included.Known Issues
Notes
- JBoss EAP 7.4 Update 13+ contains some bug fixes that did not make it into EAP 8.0 GA, it is recommended you move to EAP 8.0 latest Update
- Red Hat Insights is available for JBoss EAP 7.4 Update 11+ and accessible on the This content is not included.Red Hat Hybrid Cloud Console, see more details.
- Helm Chart for EAP 7.4 Updates
- The EAP natives for s390x platform (IBM zSeries) are only supported in the OpenShift environment on IBM zSeries, i.e bare metal installations on IBM zSeries are not supported.
- Some JBoss EAP image templates depend on other products that may not have a s390x build, see here for more details
- The Helm Chart for JBoss EAP 7.4 / JBoss EAP XP 3 allows to build and deploy applications on OpenShift using Helm package manager
- The IBM WebSphere MQ broker was updated to 9.2 for integration testing, see the Red Hat JBoss Enterprise Application Platform (EAP) 7 Tested Integrations for more details.
- Hibernate Search 5 APIs Deprecated in JBoss EAP 7.4 that will be changed in EAP 8 / Hibernate 6
- The RHSSO Galleon Layer is deprecated in JBoss EAP 7.4, see more details.
- JBoss EAP 7.4 Update 8+ now supports OpenJDK 17 / Oracle JDK 17, see configuration changes needed here.
- Deprecated in Red Hat Enterprise Application Platform (EAP) 7
- jndi-name has been required for admin-object definitions as per the schema, the server will require it to be specified or will result in an error, see more details here