This page is intended to be an overview and central hub for pages related to memory usage, leaks, and troubleshooting in uPortal.
Stub
This page is a stub. You can help it grow into a full-fledged page by adding insights and links.
Understanding the problem
There are outright bugs that result in Memory Leaks. There are also non-defect issues in the way uPortal uses memory – the way it uses memory isn't necessarily a bug so much as something to understand and tune for. You can monitor the memory usage of your uPortal.
JVM configuration
See also the page on JVM Configurations and particularly that on uPortal Heap Tuning. A JVM can be configured to more optimally host uPortal in regards to memory.
Fixing memory problems
Some code changes can be made to improve the way uPortal handles memory. There are also things you can do to troubleshoot OutOfMemory in your portal.
The exciting uPortal 3 answer
uPortal 3 aggressively adopts registries fronting centralized caching services, staving off the proliferation of memory-eating caches all over the place and shrinking the persistent size of sessions.