Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Red Hat JBoss Web Server 6.0 Release Notes
For Use with the Red Hat JBoss Web Server 6.0
Abstract
Providing feedback on Red Hat documentation
We appreciate your feedback on our technical content and encourage you to tell us what you think. If you’d like to add comments, provide insights, correct a typo, or even ask a question, you can do so directly in the documentation.
You must have a Red Hat account and be logged in to the customer portal.
To submit documentation feedback from the customer portal, do the following:
- Select the Multi-page HTML format.
- Click the Feedback button at the top-right of the document.
- Highlight the section of text where you want to provide feedback.
- Click the Add Feedback dialog next to your highlighted text.
- Enter your feedback in the text box on the right of the page and then click Submit.
We automatically create a tracking issue each time you submit feedback. Open the link that is displayed after you click Submit and start watching the issue or add more comments.
Thank you for the valuable feedback.
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. Red Hat JBoss Web Server 6.0
Welcome to the Red Hat JBoss Web Server version 6.0 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_clustermodule. Themod_clusterlibrary enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuringmod_cluster, or for information about installing and configuring alternative load balancers such asmod_jkandmod_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 Apache Tomcat 10.1 and fixes some security issues.
This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8.
Chapter 2. New features and enhancements
Red Hat JBoss Web Server 6.0 includes the following new features and enhancements.
2.1. Apache Tomcat 10.1 support
The JBoss Web Server 6.0 release is based on Apache Tomcat 10.1.8. This version of Apache Tomcat implements the following specifications that the Jakarta Enterprise Edition (EE) 10 platform requires:
2.2. Java package namespace changes from javax to jakarta
With the introduction of Apache Tomcat 10.1 support, which implements Jakarta EE 10, a major difference between JBoss Web Server 6.0 and previous product versions is the renaming of the Jakarta EE API Java packages from javax. to jakarta..
This change does not affect javax packages that are part of Java Standard Edition (SE).
Adapting to this namespace change is the biggest change involved in migrating applications to JBoss Web Server 6.0. For more information, see Migrating applications from Red Hat JBoss Web Server 5.x to Red Hat JBoss Web Server 6.
2.3. Naming enhancements for JBoss Web Server native archive files
From JBoss Web Server 6.0 onward, the native archive files that you can download from the Red Hat Customer Portal use the following naming format:
jws-6.X.x-optional-native-components-<platform>-<architecture>.zip
This supersedes the behavior in previous releases where the native archive files used the following naming format:
jws-5.X.x-application-server-<platform>-<architecture>.zip
2.4. ARM64 architecture support
JBoss Web Server 6.0 introduces support for using JBoss Web Server with the ARM64 (aarch64) architecture in the OpenShift environment.
2.5. JWS for OpenShift image for OpenJDK 17
JBoss Web Server 6.0 introduces support for importing JWS for OpenShift images that are compatible with OpenJDK 17. In this release, you can import a jboss-webserver60-openjdk17-tomcat10-openshift-ubi8 image.
2.6. JWS for OpenShift environment variable enhancements
Because of modifications in Apache Tomcat connector settings, the JWS for OpenShift environment variables include the following enhancements for secure HTTPS connections:
-
JWS_HTTPS_CERTIFICATE_CHAINis a new variable that specifies the name of the certificate chain file (for example,ca-chain.cert.pem). -
JWS_HTTPS_CERTIFICATE_DIRis a new variable that specifies the name of the directory where the certificate is stored (for example,cert). -
JWS_HTTPS_CERTIFICATEnow specifies the name of the certificate file (for example,rsa-cert.pem). This supersedes the behavior in previous releases where theJWS_HTTPS_CERTIFICATEvariable specified the name of the certificate file within a secret (for example,server.crt). -
JWS_HTTPS_CERTIFICATE_KEYnow specifies the name of the certificate key file (for example,rsa-key.pem). This supersedes the behavior in previous releases where theJWS_HTTPS_CERTIFICATE_KEYvariable specified the name of the certificate key file within a secret (for example,server.key).
2.7. Enhanced default AccessLogValve pattern
From JBoss Web Server 6.0 onward, the default AccessLogValve pattern in the JWS_HOME/tomcat/conf/server.xml file also contains %S, %I, and %T replacement strings. These replacement strings enable JBoss Web Server to include the following information in access logs to help diagnose session or performance issues:
- User session ID
- Current Request thread name
- Length of time (in seconds) to process the request
Similar to previous releases, the default AccessLogValve pattern in JBoss Web Server 6.0 still contains %h, %l, %u, %t, "%r", %s, and %b replacement strings for logging other diagnostic information.
For more information about the Access Log Valve, see the Apache Tomcat documentation.
2.8. StuckThreadDetectionValve enabled by default
From JBoss Web Server 6.0 onward, the StuckThreadDetectionValve setting is enabled by default in the JWS_HOME/tomcat/conf/server.xml file. This feature is useful for detecting requests that take an excessively long time to process, which might indicate that a processing thread is stuck. By default, if the StuckThreadDetectionValve setting is enabled and a request takes more than 600 seconds (10 minutes) to process, JBoss Web Server considers that a thread is stuck.
For more information about the Stuck Thread Detection Valve, see the Apache Tomcat documentation.
Chapter 3. Deprecated features
The following features are being deprecated in this release.
3.1. Red Hat Enterprise Linux 7 support
This release removes support for the Red Hat Enterprise Linux 7 operating system. From JBoss Web Server 6.0 onward, Red Hat does not support the installation of JBoss Web Server from an archive file or RPM packages on Red Hat Enterprise Linux 7 hosts.
For more information about supported operating system versions, see OS/JVM certifications.
3.2. Window 2016 Server support
This release removes support for the Windows 2016 Server operating system. From JBoss Web Server 6.0 onward, Red Hat does not support the installation of JBoss Web Server from an archive file on Windows 2016 Server hosts.
For more information about supported operating system versions, see OS/JVM certifications.
3.3. JDK 8 support
This release removes support for using JBoss Web Server with any of the following JDK versions:
- OpenJDK 1.8.x
- Oracle JDK 1.8.x
- IBM JDK 1.8.x
For more information about supported JDK versions, see OS/JVM certifications.
3.4. APR connector support
With the introduction of Apache Tomcat 10.1 support, JBoss Web Server no longer supports use of the Apache Portable Portable (APR) native connector. From JBoss Web Server 6.0 onward, JBoss Web Server only supports use of the NIO connector or the NIO2 connector.
3.5. JWS_HTTPS_SECRET environment variable
From JBoss Web Server 6.0 onward, JWS for OpenShift no longer supports the JWS_HTTPS_SECRET environment variable. In previous releases, this environment variable specified the name of the secret that contained the certificate files for secure HTTPS connections (for example, jws-app-secret).
For more information, see JWS for OpenShift environment variable enhancements.
From JBoss Web Server 6.0 onward, Red Hat no longer provides Apache CXF and Hibernate JAR files in the jboss-web-server-6.0.x-maven-repository.zip file that you can download from the Red Hat Customer Portal.
Chapter 4. Installing the Red Hat JBoss Web Server 6.0
You can install the JBoss Web Server 6.0 on Red Hat Enterprise Linux or Microsoft Windows. For more information see the following sections of the installation guide:
Chapter 5. OS/JVM certifications
This release is supported for use with the following operating system and Java Development Kit (JDK) versions:
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 9 | x86_64 | Red Hat OpenJDK 11, Red Hat OpenJDK 17, Oracle JDK 11, Oracle JDK 17 |
| Red Hat Enterprise Linux 8 | x86_64 | Red Hat OpenJDK 11, Red Hat OpenJDK 17, Oracle JDK 11, Oracle JDK 17 |
| Microsoft Windows 2019 Server | x86_64 | Red Hat OpenJDK 11, Red Hat OpenJDK 17, Oracle JDK 11, Oracle JDK 17 |
Red Hat Enterprise Linux 7 and Microsoft Windows 2016 Server are not supported.
Chapter 6. Resolved issues
The following issues are resolved for this release:
Chapter 7. Known issues
This release includes the following known issue:
| Issue | Description |
|---|---|
| Race condition in stop under stress: Context checks block Container stop |
Chapter 8. Supported components
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.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}