|
Home > Archive > WebSphere Application Server > May 2005 > Admin Console OutOfMemory
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 |
Admin Console OutOfMemory
|
|
|
| Hello,
Some pages are not visible in the Admin Console due to OutOfMemoryErrors
(OOME). I suppose it's got to be tuned in System Administration > Deployment
Manager, but I cannot access this page due to OOME...
Restarting the DM doesn't help, so I suppose there is so much in the Cell
that the DM is legitimately getting short on heap.
I checked in <config>/cells/<cell>/nodes/<node>/servers/dmgr/server.xml, but
it doesn't seem to contain <jvmentries> tag in <processDefinition>. Which is
confirmed by wsadmin showing {initialHeapSize 0} and {maximumHeapSize 0},
while I see the actual JVM arguments are -Xms50 and -Xmx256.
Any idea how to tune the heap of the DM then ?
Thanks.
| |
| Sunit Patke 2005-05-18, 6:05 pm |
| What happens if you add these argument (-Xms and -Xmx) to
startServer.bat|sh, start dmgr using startServer.bat|sh and then tune dmgr
using Admin Console?
Sunit
"Ben_" <reply@newsgroup.com> wrote in message
news:d6fels$49mi$1@news.boulder.ibm.com...
> Hello,
>
> Some pages are not visible in the Admin Console due to OutOfMemoryErrors
> (OOME). I suppose it's got to be tuned in System Administration >
> Deployment
> Manager, but I cannot access this page due to OOME...
>
> Restarting the DM doesn't help, so I suppose there is so much in the Cell
> that the DM is legitimately getting short on heap.
>
> I checked in <config>/cells/<cell>/nodes/<node>/servers/dmgr/server.xml,
> but
> it doesn't seem to contain <jvmentries> tag in <processDefinition>. Which
> is
> confirmed by wsadmin showing {initialHeapSize 0} and {maximumHeapSize 0},
> while I see the actual JVM arguments are -Xms50 and -Xmx256.
>
> Any idea how to tune the heap of the DM then ?
>
> Thanks.
>
>
| |
|
| Hello,
I solved the issue in the meanwhile, by modifying server.xml manually and
adding the initialHeapSize and maximumHeapSize attributes on the jvmEntries.
Thanks for the suggestion anyway.
|
|
|
|
|