Monitor Memory usage and Garbage Collection in Bamboo
Usage FAQ
- Can multiple plans share a common 3rd-party directory
- Changing Bamboo database settings
- Deploying Multiple Atlassian Applications in a Single Tomcat Container
- How Bamboo processes task arguments and passes them to OS shell
- Securing your repository connection
- Changing the remote agent heartbeat interval
- Cloning a Bamboo instance
- How do I connect Bamboo to an unsupported database
- How do I shut down my elastic instances if I have restarted my Bamboo server
- How do I stop the Bamboo server from automatically configuring my remote agent's capabilities
- JUnit parsing in Bamboo
- Known issues with CVS in Bamboo
- Monitoring and Profiling Bamboo
- Monitor Memory usage and Garbage Collection in Bamboo
- Moving Bamboo-Home of an agent
- Performing a thread dump
- Restoring passwords to recover admin users
- Send Errors to stderr - Script Builder in Visual Studio WinXP to build Solutions Files
- Using Bamboo with Clover
- Working with Java libraries
- Bamboo indicates that my Ant or Maven builds failed, even though they were successful
On this page
Related content
- No related content found
A simple way to do this is to turn on garbage collection and heap dump on out of memory.
Parameters
Please add the following parameters to Bamboo
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -Xloggc:/path/to/gc.log
Note: Remember to substitute /path/to/gc.log
with a meaningful file path on your server.
GC log file location
The garbage collection traces and the heap dumps are in <bamboo-install>/gc.log
.
Additional Note
The -XX:+PrintGCTimeStamps
flag, prints when GCs happen relative to the start of the application.
Some helpful links:
http://blogs.atlassian.com/developer/2007/10/plugging_leaks_in_confluence.html
http://www.oracle.com/technetwork/articles/javase/gcportal-136937.html
Last modified on Aug 30, 2017
Related content
- No related content found
Powered by Confluence and Scroll Viewport.