|
Home > Archive > WebSphere Portal Server > February 2007 > WebSphere Portal Heap Size Utilization Degradation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WebSphere Portal Heap Size Utilization Degradation
|
|
|
| Dear All,
I am running IBM WebSphere Portal 5.1.0.1 on Windows 2003 Standard Edition, with 4GB RAM. The JDK used is IBM JDK 1.4.2. We are now in production stage.
We are having a Memory Issue as the following:
1. Our Portal now has built-in 80 portlets. Most of them are JSF Portlets and interacting with EJBs hosted under server1 (different JVM).
2. We understand that it is Windows limitation that Memory Usage for an application can not be more than 2GB, so we set WebSphere_Portal JVM maximum Heap Size to 1250MB and the same as initial Heap Size.
3. Once we started the WebSphere_Portal, the Out Of Memomry error, can not allocate initial Heap occurred. So we have to set the maximum Heap Size to 800MB.
4. FYI that a couple of months ago, the Portal only consisted of 50 portlets and we were still able to set the Maximum Heap Size to 1025MB.
5. Does it mean that the more Portlets we deploy, the less Heap we can use?
6. What does WebSphere_Portal JVM do with the remaining 1.2 GB (2GB - 800MB) so can we can not utilize them?
Regards.
| |
|
|
|
|
|