-
Suggestion
-
Resolution: Fixed
-
None
-
8
-
4
-
We should allow free-form JVM arguments instead of the ones defined with -D prefix in the synchrony-args.properties.
Workaround
It is possible to add the GC Logging JVM arguments in the start-synchrony.sh for Data Center if you choose to setup the Synchrony Cluster yourself in the Confluence Data Center.
- Locate the line JAVA_OPTS="-Xss2048k -Xmx2g"
- Modify it as below:
Example of adding GC Logging arguments
JAVA_OPTS="-Xss2048k -Xmx2g -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+PrintTenuringDistribution -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -Xloggc:<synchrony-directory-path>/gc.log"
This workaround doesn't apply to :
- Confluence Standalone Server
- Confluence Managed Synchrony in Data Center from v6.12 and above
Other options: How to monitor the Synchrony cluster health
- is duplicated by
-
CONFSERVER-55899 How to monitor Synchrony traffic using Dynatrace
- Closed
- relates to
-
CONFSERVER-58401 Increase managed Synchrony JVM maximum memory to at least 2GB
- Closed
- was split from
-
CONFSERVER-45083 Allow JVM args to be passed to Synchrony.
- Closed
- Mentioned in
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...