Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Red Hat JBoss Web Server 6.2 Release Notes

Red Hat JBoss Web Server 6.2

For Use with the Red Hat JBoss Web Server 6.2

Red Hat Customer Content Services

Abstract

These release notes contain important information related to the Red Hat JBoss Web Server 6.2.

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 Create creates and routes the issue to the appropriate documentation team.

Making open source more inclusive
Copy link

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. Red Hat JBoss Web Server 6.2
Copy link

Welcome to the Red Hat JBoss Web Server version 6.2 release.

Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library.

JBoss Web Server includes the following key components:

  • Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1.
  • The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies.
  • Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server.
  • The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster, or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy, see the Apache HTTP Server Connectors and Load Balancing Guide.
  • Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides.
  • OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides.

This release introduces support for Java 25.

This release of JBoss Web Server provides OpenShift images built on Universal Base Image (UBI) 8. It also provides OpenShift images built on UBI 9 as a Technology Preview feature.

Chapter 2. New features and enhancements
Copy link

Red Hat JBoss Web Server 6.2 includes the following new features and enhancements.

Java 25 support

JBoss Web Server 6.2 is now certified for use with Red Hat build of OpenJDK 25 and Oracle JDK 25.

Note

Java 25 is now fully tested and supported for both RPM package and archive file distributions of JBoss Web Server 6.2.

Uninstallation script for archive file distributions on RHEL

JBoss Web Server 6.2 provides a JWS_HOME/tomcat/.uninstall-jws script that you can use to uninstall Red Hat JBoss Web Server if it was installed from an archive file distribution on RHEL.

The usage string for the .uninstall-jws script is as follows: 

sudo ./.uninstall-jws [--yes] [--purge] [--purge-user] [--kill-user-procs] [--remove-sysconfig]
Copy to Clipboard Toggle word wrap

Consider the following usage information:

  • Use of the .uninstall-jws script requires sudo privileges.
  • This script is only available for use with archive file distributions on RHEL. It is not available for use with RPM package distributions on RHEL or archive file distributions on Windows.
  • If you have chosen to manage your JBoss Web Server installation from the command line instead of running the .postinstall/systemd script, you can still use the .uninstall-jws script. In this situation, the .uninstall-jws script can remove those parts of the installation that match the .postinstall/systemd default setup. However, the uninstallation script will skip removal of any parts of the installation that differ from the default setup.

  • When you run the .uninstall-jws script, it always attempts to perform the following tasks:

    • Stop the service (if found).
    • Remove service files (if found).
    • Remove the jws6-tomcat.conf file (if found).
    • Remove the SELinux module (if found).

  • You can also specify the following options to instruct the script to perform additional actions:

    • Specify the --purge option to delete the <JWS_HOME> directory.
    • Specify the --purge-user option to delete the tomcat user and group.
    • Specify the --kill-user-procs option to stop any remaining processes for the tomcat user before user removal. (This action requires that you also specify the --purge-user option.)
    • Specify the --remove-sysconfig option to remove the /etc/sysconfig/jws6-tomcat directory (if present).

  • By default, the .uninstall-jws script displays confirmation prompts to request your approval before it performs any destructive operations, such as deleting the <JWS_HOME> directory or the tomcat user and group. If you want to disable prompts, specify the --yes option.

    For example, if you run sudo ./.uninstall-jws --purge, the script prompts you for your approval before it deletes the <JWS_HOME> directory. Conversely, if you run sudo ./.uninstall-jws --yes --purge, the script automatically deletes the <JWS_HOME> directory without prompting you.

JWS for OpenShift images on UBI 9 (Technology Preview)

JBoss Web Server 6.2 introduces JWS for OpenShift images that are built on Universal Base Image (UBI) 9 as a Technology Preview feature.

For more information about importing the jboss-webserver62-openjdk17-tomcat10-openshift-ubi9 or jboss-webserver62-openjdk21-tomcat10-openshift-ubi9 image, see the RHEA-2026:2820 advisory.

Important

JWS for OpenShift images built on UBI 9 are a Technology Preview feature only in this release. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

Chapter 3. Deprecated features
Copy link

The following features are deprecated in this release.

JWS for OpenShift images on UBI 8

This release deprecates the use of JWS for OpenShift images that are built on UBI 8.

Note

Red Hat still provides JWS for OpenShift images built on UBI 8 as part of this release. Red Hat plans to stop providing JWS for OpenShift images built on UBI 8 in a future release.

You can install the JBoss Web Server 6.2 on Red Hat Enterprise Linux or Windows Server. For more information see the following sections of the installation guide:

Chapter 5. OS/JVM certifications
Copy link

This release is supported for use with the following operating system and Java Development Kit (JDK) versions:

Expand
Operating SystemChipset ArchitectureJava Virtual Machine

Red Hat Enterprise Linux 10

x86_64

  • Red Hat build of OpenJDK 11
  • Red Hat build of OpenJDK 17
  • Red Hat build of OpenJDK 21
  • Oracle JDK 11
  • Oracle JDK 17
  • Oracle JDK 21

Red Hat Enterprise Linux 9

x86_64

  • Red Hat build of OpenJDK 11
  • Red Hat build of OpenJDK 17
  • Red Hat build of OpenJDK 21
  • Oracle JDK 11
  • Oracle JDK 17
  • Oracle JDK 21

Red Hat Enterprise Linux 8

x86_64

  • Red Hat build of OpenJDK 11
  • Red Hat build of OpenJDK 17
  • Red Hat build of OpenJDK 21
  • Oracle JDK 11
  • Oracle JDK 17
  • Oracle JDK 21

Windows Server 2022

x86_64

  • Red Hat build of OpenJDK 11
  • Red Hat build of OpenJDK 17
  • Red Hat build of OpenJDK 21
  • Oracle JDK 11
  • Oracle JDK 17
  • Oracle JDK 21

Windows Server 2019

x86_64

  • Red Hat build of OpenJDK 11
  • Red Hat build of OpenJDK 17
  • Red Hat build of OpenJDK 21
  • Oracle JDK 11
  • Oracle JDK 17
  • Oracle JDK 21

Chapter 6. Resolved issues
Copy link

The following issues are resolved for this release:

Expand
IssueDescription

JWS-3699

[ASF BZ 69866] OpenSSLContexts leak across reload through JNI global reference when using truststore

JWS-3620

FileStore used with PersistentValve can cause EOFException during session expiration checks and dropped session

JWS-3429

JWS zip version.sh breaks after .postinstall.selinux

JWS-3267

tomcat-digest in JWS RPM fails if called as non-root user

Chapter 7. Known issues
Copy link

There are no known issues for this release.

Chapter 8. Supported components
Copy link

For a list of component versions that are supported in this release of Red Hat JBoss Web Server, see the JBoss Web Server Component Details page.

Legal Notice
Copy link

Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . 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, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.
The OpenStack® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top