We've been using Bamboo for a couple months and noticed that when you install a remote agent as a Windows service it starts to consume vast amounts of virtual memory to the point where the service needs to be stopped and restarted.
Is there something in the remote agent configuration that can be edited to limit virtual memory use or is this a memory leak with the remote agent code?
Java programs eat as much memory as you give them. The default for heap is 512MB (there are some other memory types than heap, but heap is the biggest one). That limit is enforced by Java and the agent cannot exceed it.
If the agent reaches 500-700MB and stays there, that's normal. If it runs out of memory (dies / shows OutOfMemory errors), you should contact support. They will ask you for a heap dump, so if you know how to create it, you should attach it to the issue.
You can decrease the upper memory limit by modifying wrapper.java.maxmemory in the wrapper.conf file located in your agent home directory. You should be able to reduce it to 256MB without much problems - but if you run of memory, keep in mind that's unsupported.
Are you a whiz at handling tickets and looking at how you can further optimize your workflow with automation? Do you tackle detailed customer support questions while simultaneously getting flooded wi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG