Red Hat JBoss Core Services Apache HTTP Server 2.4.51 Release Notes

Red Hat JBoss Core Services 2.4.51

For Use with the Red Hat JBoss Core Services Apache HTTP Server 2.4.51

Red Hat Customer Content Services

Abstract

These release notes contain important information related to the Red Hat JBoss Core Services Apache HTTP Server 2.4.51.

Preface

Welcome to the Red Hat JBoss Core Services version 2.4.51 release.

Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation. The Apache HTTP Server includes the following features:

  • Implements the current HTTP standards, including HTTP/1.1 and HTTP/2
  • Supports Transport Layer Security (TLS) encryption through OpenSSL, which provides secure connections between the web server and web clients.
  • Supports extensible functionality through the use of modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server.

Providing feedback on Red Hat documentation

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.

Procedure

  1. Click the following link to create a ticket.
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. New features and enhancements

Red Hat JBoss Core Services 2.4.51 includes the following new features and enhancements.

1.1. Renaming of mod_cluster-native to mod_proxy_cluster

From JBCS 2.4.51 onward, mod_cluster-native has been renamed mod_proxy_cluster.

The following name changes have been introduced in this release:

  • The jbcs-httpd24-mod_cluster-native package has been renamed jbcs-httpd24-mod_proxy_cluster.
  • The mod_cluster.conf file has been renamed mod_proxy_cluster.conf.
  • The mod_cluster cache has been renamed mod_proxy_cluster.
  • The mod_cluster SELinux policy has been renamed mod_proxy_cluster.
  • References to the mod_cluster connector in JBCS product documentation have been changed to mod_proxy_cluster.

1.2. Default MPM is event on Red Hat Enterprise Linux 8

From JBCS 2.4.51 onward, the event multi-processing module (MPM) is set as the default MPM on Red Hat Enterprise Linux 8. This supercedes the behavior in previous releases where the prefork MPM was set as the default.

Note

This change applies to the default MPM on Red Hat Enterprise Linux 8 only. The prefork MPM remains the default MPM on Red Hat Enterprise Linux 7.

1.3. Configuration of MPM performance settings in the mpm.conf file

From JBCS 2.4.51 onward, the JBCS_HOME/httpd/conf.d/mpm.conf file now contains the performance settings for multi-processing modules (MPMs). This supersedes the behavior in JBCS 2.4.37 or earlier releases where the JBCS_HOME/httpd/conf.modules.d/00-mpm.conf file contained these MPM performance settings.

Important

If you are upgrading from JBCS 2.4.37 or earlier, ensure that you configure the conf.d/mpm.conf file for your upgraded 2.4.51 installation to match any customized settings that you previously configured in conf.modules.d/00-mpm.conf. Otherwise, your upgraded JBCS 2.4.51 installation automatically uses the default settings in the conf.d/mpm.conf file, which might lead to unexpected performance issues.

Note

In JBCS 2.4.51, the JBCS_HOME/httpd/conf.modules.d/00-mpm.conf file still contains the LoadModule directives for MPM types, as in previous releases.

Chapter 2. Installing the Red Hat JBoss Core Services 2.4.51

You can install the Apache HTTP Server 2.4.51 on Red Hat Enterprise Linux or Microsoft Windows. For more information see the following sections of the installation guide:

Chapter 3. Upgrading to the Red Hat JBoss Core Services Apache HTTP Server 2.4.51

If you have installed an earlier version of the Red Hat JBoss Core Services Apache HTTP Server from an archive file, you must perform the following steps to upgrade to the Apache HTTP Server 2.4.51:

  1. Install the Apache HTTP Server 2.4.51.
  2. Set up the Apache HTTP Server 2.4.51.
  3. Remove the earlier version of Apache HTTP Server.

Prerequisites

  • If you are using Red Hat Enterprise Linux, you have root user access.
  • If you are using Windows Server, you have administrative access.
  • The Red Hat JBoss Core Services Apache HTTP Server 2.4.37 or earlier was previously installed in your system from an archive file.

Procedure

You can use the following recommended procedure to upgrade the Red Hat JBoss Core Services Apache HTTP Server from version 2.4.37 to version 2.4.51:

  1. Shut down any running instances of the Red Hat JBoss Core Services Apache HTTP Server 2.4.37.
  2. Back up the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 installation and configuration files.
  3. Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 by using the archive file installation method for the current system (see Additional Resources below).

  4. Migrate your configuration from the Red Hat JBoss Core Services Apache HTTP Server version 2.4.37 to version 2.4.51.

    Note

    The Apache HTTP Server configuration files might have changed since the Apache HTTP Server 2.4.37 release. Update the 2.4.51 version configuration files rather than overwrite them with the configuration files from a different version (such as the Apache HTTP Server 2.4.37).

  5. Remove the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 root directory.

Additional Resources

Chapter 4. Resolved issues

The following are resolved issues for this release:

IssueSummary

JBCS-1388

RHEL-9 zip name missing -GA.<BUILD>

JBCS-1387

mod_proxy_cluster hcheck not working

JBCS-1361

[DDF] The back-end configuration in the LB Config Tool is "JWS/Tomcat", not "Tomcat"

JBCS-1352

JBCS-2.4.51-GA-ER2 contains both conf.d/mpm.conf and conf.modules.d/00-mpm.conf

JBCS-1351

JBCS-2.4.51-GA-ER2 contains mod_cluster.conf instead of mod_proxy_cluster.conf

JBCS-1289

mod_ext_filter test failure

JBCS-1288

Unexpected library name change libexpat.dll

JBCS-1287

Unexpected dependency in libxml2.dll

JBCS-1286

htdbm fails to create user

JBCS-1285

Apxs doesn’t work using JBCS src headers and Libs

JBCS-1260

Remove lua package from JBCS distribution

JBCS-1227

Documentation needs to be updated to reflect release of JBCS httpd rpm on RHEL8

JBCS-1204

.postinstall script breaks the JBCS manual

JBCS-1196

[DDF] After enabling the jb-coreservices-1-for-rhel-8-x86_64-rpms repository, running `dnf --disablerepo='*'

JBCS-1181

default mod_jk location for JkShmFile should be moved from logs/jk.shm due to SELinux

JBCS-1148

Rename mod_cluster-native package to mod_proxy_cluster

JBCS-1073

responsefieldsize needs to be configurable for mod_cluster

JBCS-987

The default worker install is prefork we should use a more modern one like event

JBCS-811

Reduce postinstalls complexity

JBCS-544

Duplicate licence files in Openssl

JBCS-452

openssl warning message

JBCS-332

mpm_event_module default example configuration is missing from 00-mpm.conf

JBCS-66

Socket bind failed on link-local [IPV6]

Chapter 5. Known issues

The following are known issues for this release:

IssueSummary

JBCS-1353

mpm_event_module instead of event.c in mpm.conf

JBCS-1293

the xml files are missing in docs/manual/ in the look aside gerrit

Chapter 6. Supported components

For a list of component versions that are supported in this release of Red Hat JBoss Core Services, see the Core Services Apache HTTP Server Component Details page. Before you attempt to access the Component Details page, you must ensure that you have an active Red Hat subscription and you are logged in to the Red Hat Customer Portal.

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.