Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Meridian-2019.1.1, 25.1.1
-
Fix Version/s: Meridian-2019.1.9, 26.1.2
-
Component/s: Example configuration files
-
Security Level: Default (Default Security Scheme)
-
Environment:Any system using JDK 11
https://mynms.opennms.com/Ticket/Display.html?id=6571
-
Sprint:Horizon 2020 - May 27, Horizon 2020 - June 10, Horizon 2020 - June 24
Description
At least the following options listed in etc/examples/opennms.conf break startup with JDK11:
-d64 (evidently had an effect only on Solaris anyway, RIP)
-XX:+PrintGCTimeStamps / -XX:+UseGCLogFileRotation / bunch of other -XX flags about GC logging have been unified into incantations of the new -Xlog flag.
Here's an example that starts up successfully and approximates the GC-logging accomplished by the old flags under JDK8:
ADDITIONAL_MANAGER_OPTIONS="${ADDITIONAL_MANAGER_OPTIONS} -XX:+UseStringDeduplication"
# Garbage Collection
ADDITIONAL_MANAGER_OPTIONS="${ADDITIONAL_MANAGER_OPTIONS} -Xlog:gc*=info:file=/opt/opennms/logs/gc.log::filecount=4,filesize=20M"
ADDITIONAL_MANAGER_OPTIONS="${ADDITIONAL_MANAGER_OPTIONS} -XX:+UseG1GC"
