Show Table of Contents Hide Table of Contents English English Multi-page HTML Single-page HTML PDF ePub Red Hat JBoss Web Server 5.0 release notesPreface1. Why we skipped Red Hat JBoss Web Server 42. Change to the structure of the Red Hat JBoss Web Server3. Key new features and enhancements in the Red Hat JBoss Web Server 5.03.1. Based on Apache Tomcat 9.0.7:3.1.1. HTTP/2 support3.1.2. Support for using OpenSSL for TLS support with the JSSE connectors (NIO and NIO2)3.1.3. The NIO connector is the default for HTTP/1.1 connections when the tomcat-native is installed3.1.4. Support for TLS virtual hosting (SNI)3.2. System daemon integration scripts provided for the Red Hat Enterprise Linux users installing from .zip archives3.3. The tomcat-vault installation process has been improved3.4. The vault.properties file for tomcat-vault can be stored outside JWS_HOME3.5. Change in manager and host-manager webapp behavior3.6. Change to mod_cluster 1.4 - a connector needs to be specified.3.7. Allows the configuration of multiple properties files3.8. Logging JBoss Web Server with log4j deprecated3.9. Changes to JBoss Web Server Plus3.10. Tomcat embedded included in the Red Hat JBoss Web Server 5.0 maven repository4. Technology Previews for the Red Hat JBoss Web Server 5.04.1. Technology Preview: Deploying Narayana on the Red Hat JBoss Web Server 5.05. Installing the Red Hat JBoss Web Server 5.06. Upgrading JBoss Web Server7. Resolved issues8. Known issues9. Components included in Red Hat JBoss Web Server 5.0Legal Notice Red Hat JBoss Web Server 5.0 release notes Red Hat JBoss Web Server 5.0For Use with the Red Hat JBoss Web Server 5.0Red Hat Customer Content Services Legal NoticeAbstract These release notes contain important information related to the Red Hat JBoss Web Server 5.0. Preface Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.