Resolving Incompatible JVM Options when Migrating to JBoss EAP 8 with Java 17

Solution Unverified - Updated -

Issue

Upon upgrading from JBoss EAP 7.3 to 8.0, users experienced issues with previously used JVM settings for performance tuning, particularly those that relied on the now-obsolete CMS garbage collector in Java 17. As a result, some VM options were unrecognized or deprecated.

Environment

  • JBoss EAP
    • 7.4.7+
    • 8.x
  • Java 17

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content