Deprecated JVM tuning options might affect broker migration from Java 8 to Java 11 and later
Issue
The Artemis tuning guide [1] no longer recommends deprecated JVM tuning options like -XX:+AggressiveOpts and -XX:+UseFastAccessorMethods although earlier versions (e.g., [2]) did. There are doubtless AMQ 7 installations in the field that are making use of these options. Although the removal of these options from the JVM command line may be sufficient to restore Java 11 compatibility, it isn't clear what effect this change has on broker tuning.
[1] https://activemq.apache.org/components/artemis/documentation/latest/perf-tuning.html
[2] https://activemq.apache.org/components/artemis/documentation/2.1.0/perf-tuning.html
Environment
- Red Hat AMQ
- 7.9 and later
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.