GC changes after JDK upgrade in EAP domain mode

Solution Verified - Updated -

Issue

  • When change OpenJDK version to version 11 without any JVM options change for GC, the CLI:
    /host=slave/server=server-one/core-service=platform-mbean/type=garbage-collector/name=PS_MarkSweep
    causes an error in the log:
        2020-11-19 17: 03: 51,037 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool - 90) WFLYCTL0013: Operation         ("read-attribute") failed - address: ([
            ("core-service" => "platform-mbean"),
            ("type" => "garbage-collector"),
            ("name" => "PS_MarkSweep")
        ]) - failure description: "WFLYPMB0008: No GarbageCollectorMXBean with name PS_MarkSweep currently exists"
  • If HC node 1 is running using JDK 8 and HC node 2 is running using JDK 11, the CLI
    /host=slave-two/server=server-one/core-service=platform-mbean/type=garbage-collector/name=PS_MarkSweep
    run on HC node 2 will causes an error in the log.

Environment

  • OpenJDK
    • 8
    • 11
  • JBoss Enterprise Application Platform (EAP)
    • 7.3
    • domain mode
      - Host Controller (HC) node 1 OpenJDK 8
      - Host Controller (HC) node 2 OpenJDK 11
      - no Garbage Collection (GC) options are set for servers

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