Hi Team,
Does the below mentioned interim mitigation applies for latest version LTS Jira (10.3.27) & Confluence DC (9.2.28) ?
Confluence Data Center
For standard deployments:
1. Pass the following JVM flags to the application at startup:
For Linux <confluence-install>/bin/setenv.sh:
CATALINA_OPTS="-XX:UseAVX=2 -Dconversion.sandbox.java.options=\"-XX:+IgnoreUnrecognizedVMOptions,-XX:UseAVX=2\" ${CATALINA_OPTS}"
For Windows Service (add as a new line) in the Java Options box:
-XX:UseAVX=2-Dconversion.sandbox.java.options=-XX:UseAVX=2,-XX:+IgnoreUnrecognizedVMOptions
See Configuring System Properties | Confluence Data Center 11.0 | Atlassian Documentation
2. Update <confluence-home>/synchrony-args.properties and/or <confluence-shared-home>/synchrony-args.properties (if the file is present) with these two new lines:
synchrony.jvm.arg.jdk1=-XX:+IgnoreUnrecognizedVMOptionssynchrony.jvm.arg.jdk2=-XX:UseAVX=2
3. Restart Confluence
Jira Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Further details can be found here: Setting properties and options on startup | Administering Jira applications Data Center 11.3 | Atla…
Jira Service Management Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Further details can be found here: Setting properties and options on startup | Administering Jira applications Data Center 11.3 | Atla…