-
Suggestion
-
Resolution: Duplicate
-
None
-
None
The current Memory information for the system information page can be confusing to users. As it basically reports to you the current memory usage levels, this can be misleading and result in users to believing the JVM parameters parsed to the JVM do not take effect or have not been configured correctly when in fact they have.
For example, when setting the boundaries for the memory with varying -Xms and -Xmx settings, Confluence initially shows memory usage up to the minimum memory setting. As the usage increases, it will eventually be updated in the system info page to reflect the current usage levels.
Example, this is the current Heap size settings for my 2.8.0 instance:
# Initial Java Heap Size (in MB) wrapper.java.initmemory=512m # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=756m
The screenshot shows the current total at 508 MB. Some users with this configuration would expect to see total memory as 756 MB instead. Perhaps we can include a script that can be run to retrieve memory information on demand? I've attached an example jsp i wrote which grabs information on the current JVM properties:
# Java version: 1.5.0_13 # Java Home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home # Java classpath: ../wrapper/lib/wrapper.jar:/Library/Java/Home/lib/tools.jar:../bin/bootstrap.jar # Total Memory: 532873216 # Max Memory: 786628608 # Free Memory: 386200112
Something like this could be useful for checking and validating actual memory settings rather than the current usage.
- duplicates
-
CONFSERVER-16298 Improve System Information reporting
- Closed
- is incorporated by
-
CONFSERVER-14261 Expand Sys Info
- Closed
- is related to
-
CONFSERVER-9719 Add information about (outbound HTTP) proxy settings to System Info
- Closed
-
CONFSERVER-54227 Add information about (outbound HTTP) proxy settings to System Info
- Closed