-
Type:
Suggestion
-
Resolution: Obsolete
-
None
-
Component/s: Documentation - All
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Problem
There are a number of articles in the documentation space that are related to heap dump generation and garbage collection logging. These articles mention how to permanently change the related setting, but not how you can alter those while the application is running.
Suggestion
I have created a KB explaining how some of the related parameters can be changed runtime. Please link to this article from the related documentation: https://confluence.atlassian.com/display/KB/How+to+change+JVM+arguments+at+runtime+to+avoid+application+restart.
Reference/affected articles
- https://confluence.atlassian.com/doc/generating-a-heap-dump-219024032.html
- https://confluence.atlassian.com/stashkb/how-to-generate-a-heap-dump-717062495.html
- https://confluence.atlassian.com/confkb/how-to-get-a-java-heap-dump-213523770.html
- https://confluence.atlassian.com/jirakb/using-memory-dumps-to-analyze-outofmemoryerrors-227416007.html
- https://confluence.atlassian.com/enterprise/garbage-collection-gc-tuning-guide-461504616.html
- https://confluence.atlassian.com/jirakb/using-garbage-collection-logs-to-analyze-jira-application-performance-227416009.html
- https://confluence.atlassian.com/conf53/garbage-collector-performance-issues-411109189.html
- https://confluence.atlassian.com/confkb/how-to-enable-garbage-collection-gc-logging-300813751.html
- https://confluence.atlassian.com/doc/garbage-collector-performance-issues-200707997.html
- https://confluence.atlassian.com/enterprise/garbage-collection-gc-tuning-guide-461504616.html
- https://confluence.atlassian.com/display/FISHKB/Fix+Out+of+Memory+errors (changed but pending for details on default location for garbage location log since Xloggc cannot be set at runtime)
- relates to
-
CONFCLOUD-41299 Documentation request: Mention runtime JVM parameter change option in related docs
- Closed