<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi" -->

---
title: Upgrading to Red Hat JBoss Web Server 7: Key changes &...
description: Red Hat JBoss Web Server 7 is now generally available, bundling Apache Tomcat 11.0.21, Jakarta EE 11, and requiring Java 17 as the new baseline. Unlike the JWS...
canonical: https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts | daily.dev
og:description: Red Hat JBoss Web Server 7 is now generally available, bundling Apache Tomcat 11.0.21, Jakarta EE 11, and requiring Java 17 as the new baseline. Unlike the JWS...
og:url: https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi
og:image: https://api.daily.dev/og/posts/8s8ps7IMI.png
og:image:alt: Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts

**[Red Hat Developer](https://daily.dev/sources/rhdev)** · 8 min read · 0 upvotes · 0 comments

## Summary

Red Hat JBoss Web Server 7 is now generally available, bundling Apache Tomcat 11.0.21, Jakarta EE 11, and requiring Java 17 as the new baseline. Unlike the JWS 5-to-6 upgrade, no javax-to-jakarta import renaming is needed this time, but several Tomcat 11 behavioral changes can break existing deployments: parameter parsing now throws exceptions instead of returning null, FailedRequestFilter has been removed, maxParameterCount defaults dropped from 10,000 to 1,000, HTTP/2 server push is gone (newPushBuilder returns null), Prometheus is no longer bundled in the base image, and cookie quoting now follows RFC 6265 strictly. Java 17 migration risks include strong encapsulation blocking reflective access and bytecode manipulation libraries (ASM, Byte Buddy, cglib, Javassist) needing updates for Hibernate, Spring, and Mockito compatibility. The SecurityManager has been completely removed, requiring a shift to container-based isolation. JWS for OpenShift now builds exclusively on UBI 9, dropping UBI 8 support, while Spring Boot 4 deployment on JWS 7 works technically but falls outside official Red Hat support.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://developers.redhat.com/articles/2026/09/28/upgrading-red-hat-jboss-web-server-7-key-changes-impacts>

## Questions this post answers

### What happens to getParameter() in Tomcat 11 when a request parameter fails to parse?

Tomcat 11, used in JBoss Web Server 7, throws a runtime exception instead of returning null when a request body is malformed or exceeds a size limit. Previously Tomcat silently returned null from getParameter(), making it impossible to distinguish a missing field from a failed parse. Code that treats a null parameter as its error path will break after upgrading.

_Teams upgrading Tomcat can track breaking parameter-parsing changes like this one on daily.dev._

### Why does FailedRequestFilter need to be removed when upgrading to JBoss Web Server 7?

FailedRequestFilter has been removed entirely in Tomcat 11, which ships with JBoss Web Server 7. It existed only as a workaround that checked a request attribute Tomcat set on a parse failure, but since the API now throws exceptions directly, the filter is unnecessary. Any reference left in web.xml will prevent the application from starting.

_Reviewing web.xml cleanup steps like this is easier when tracking JBoss and Tomcat upgrade notes on daily.dev._

### Does JBoss Web Server 7 still support the Java SecurityManager?

No, the Java SecurityManager is completely removed in Tomcat 11 and JBoss Web Server 7, following the JDK's own deprecation for removal. Applications relying on -Djava.security.manager and catalina.policy to sandbox untrusted code sharing an instance lose that mechanism entirely. Red Hat recommends achieving equivalent isolation through containers, running one web application per instance.

_Planning a SecurityManager removal migration is simpler when following breaking-change coverage on daily.dev._

## Similar posts on daily.dev

- [Deploy and customize JBoss Web Server on Red Hat OpenShift](https://daily.dev/posts/deploy-and-customize-jboss-web-server-on-red-hat-openshift-umpsaq3m0) · Red Hat Developer · 0 upvotes · 0 comments
- [Jakarta EE 11, Spring Boot 4.0, and more in 26.0.0.5](https://daily.dev/posts/jakarta-ee-11-spring-boot-4-0-and-more-in-26-0-0-5-warfegyiu) · Jakarta EE · 2 upvotes · 0 comments
- [What's New in the May 2026 Payara Platform Release](https://daily.dev/posts/what-s-new-in-the-may-2026-payara-platform-release-cnklpivua) · Foojay.io · 0 upvotes · 0 comments
- [Java Weekly, Issue 622](https://daily.dev/posts/java-weekly-issue-622-yhsvtmyww) · Baeldung · 3 upvotes · 0 comments

---

Tags: [#java](https://daily.dev/tags/java), [#jakarta-ee](https://daily.dev/tags/jakarta-ee)

[View this post on daily.dev](https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Upgrading to Red Hat JBoss Web Server 7: Key changes \u0026 impacts","url":"https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi"},"datePublished":"2026-09-28T13:21:05.899Z","dateModified":"2026-09-28T13:21:32.574Z","description":"Red Hat JBoss Web Server 7 is now generally available, bundling Apache Tomcat 11.0.21, Jakarta EE 11, and requiring Java 17 as the new baseline. Unlike the JWS...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","isAccessibleForFree":true,"articleSection":"Red Hat Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Red Hat Developer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a8895f3216c4900bdc455585a4ad3e4","url":"https://daily.dev/sources/rhdev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"java,jakarta-ee","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Red Hat Developer","item":"https://daily.dev/sources/rhdev"},{"@type":"ListItem","position":3,"name":"Upgrading to Red Hat JBoss Web Server 7: Key changes \u0026 impacts"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/upgrading-to-red-hat-jboss-web-server-7-key-changes-impacts-8s8ps7imi#faq","mainEntity":[{"@type":"Question","name":"What happens to getParameter() in Tomcat 11 when a request parameter fails to parse?","acceptedAnswer":{"@type":"Answer","text":"Tomcat 11, used in JBoss Web Server 7, throws a runtime exception instead of returning null when a request body is malformed or exceeds a size limit. Previously Tomcat silently returned null from getParameter(), making it impossible to distinguish a missing field from a failed parse. Code that treats a null parameter as its error path will break after upgrading. Teams upgrading Tomcat can track breaking parameter-parsing changes like this one on daily.dev."}},{"@type":"Question","name":"Why does FailedRequestFilter need to be removed when upgrading to JBoss Web Server 7?","acceptedAnswer":{"@type":"Answer","text":"FailedRequestFilter has been removed entirely in Tomcat 11, which ships with JBoss Web Server 7. It existed only as a workaround that checked a request attribute Tomcat set on a parse failure, but since the API now throws exceptions directly, the filter is unnecessary. Any reference left in web.xml will prevent the application from starting. Reviewing web.xml cleanup steps like this is easier when tracking JBoss and Tomcat upgrade notes on daily.dev."}},{"@type":"Question","name":"Does JBoss Web Server 7 still support the Java SecurityManager?","acceptedAnswer":{"@type":"Answer","text":"No, the Java SecurityManager is completely removed in Tomcat 11 and JBoss Web Server 7, following the JDK's own deprecation for removal. Applications relying on -Djava.security.manager and catalina.policy to sandbox untrusted code sharing an instance lose that mechanism entirely. Red Hat recommends achieving equivalent isolation through containers, running one web application per instance. Planning a SecurityManager removal migration is simpler when following breaking-change coverage on daily.dev."}}]}
```

