WebSphere Commerce suite - OutOfMemoryError

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Commerce suite > January 2004 > OutOfMemoryError





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 OutOfMemoryError
Peter Pontbriand

2004-01-19, 2:48 pm

Our production WCS5.4BE application servers have been brought to their knees
twice in the lasy week, with OutOfMemoryError showing up in the ECMessage
log. These app servers have dedicated hosts (no HTTPServers, databases, or
anything else) with 4 Gigabytes of RAM, yet the maximum heap size for the
JVMs is configured to 384 MB. Is this reasonable, or can we increase the
heap size to deal with the OutOfMemoryError issue?

There is one store with light traffic deployed to these servers.

Are there any good resources on the web that I can turn to that
intelligently discuss this aspect of WAS performance tuning?

--
Peter Pontbriand
Software Development Manager
Gilmore


Bibhas Bhattacharya

2004-01-19, 2:48 pm

Default -Xmx values are too low for production. Two options exist:

1. Remove the max memory linit. Or,
2. Set a higher limit.

--
Bibhas Bhattacharya
--
Web Age Solutions Inc.
WebSphere and WebLogic Training and Consulting Services
www.webagesolutions.com

"Peter Pontbriand" <sprocket@spam.spam.spam.storm.ca> wrote in message
news:bp2ug1$50eu$1@news.boulder.ibm.com...
quote:

> Our production WCS5.4BE application servers have been brought to their


knees
quote:

> twice in the lasy week, with OutOfMemoryError showing up in the ECMessage
> log. These app servers have dedicated hosts (no HTTPServers, databases, or
> anything else) with 4 Gigabytes of RAM, yet the maximum heap size for the
> JVMs is configured to 384 MB. Is this reasonable, or can we increase the
> heap size to deal with the OutOfMemoryError issue?
>
> There is one store with light traffic deployed to these servers.
>
> Are there any good resources on the web that I can turn to that
> intelligently discuss this aspect of WAS performance tuning?
>
> --
> Peter Pontbriand
> Software Development Manager
> Gilmore
>
>




Glen Burson

2004-01-19, 2:48 pm

Hi Peter,

As Bibhas says, 384 meg is probably too low, although having said that we
ran a high throughput site with only 384 meg for a long time with no
problems (now we have 512 meg).

Your best bet would be to turn on verbose gc (from the JVM options in the
WebSphere admin console) then monitor the standard out. You should read the
JVM diagnostics guide to understand the output and more about memory
issues - it's not a small subject!

http://www-106.ibm.com/developerwor...diag131rev1.pdf

Cheers,
Glen.

"Peter Pontbriand" <sprocket@spam.spam.spam.storm.ca> wrote in message
news:bp2ug1$50eu$1@news.boulder.ibm.com...
quote:

> Our production WCS5.4BE application servers have been brought to their


knees
quote:

> twice in the lasy week, with OutOfMemoryError showing up in the ECMessage
> log. These app servers have dedicated hosts (no HTTPServers, databases, or
> anything else) with 4 Gigabytes of RAM, yet the maximum heap size for the
> JVMs is configured to 384 MB. Is this reasonable, or can we increase the
> heap size to deal with the OutOfMemoryError issue?
>
> There is one store with light traffic deployed to these servers.
>
> Are there any good resources on the web that I can turn to that
> intelligently discuss this aspect of WAS performance tuning?
>
> --
> Peter Pontbriand
> Software Development Manager
> Gilmore
>
>




Bibhas Bhattacharya

2004-01-19, 2:48 pm

> 1. Remove the max memory linit. Or,

I should correct myself. Removing the max memory limit will cause the JVM to
pick a default max memory. This default is often too low in some operating
systems. So there is really one option: set a very high max limit. A high
number is does not mean that system will actually allocate all that memory.
JVM will only allocate as much memory as necessary (peak memory usage + 30%
for free space). So it is rather harmless to set a high number.

--
Thank you,

Bibhas Bhattacharya
--
Web Age Solutions Inc.
WebSphere and WebLogic Training and Consulting Services
www.webagesolutions.com

"Bibhas Bhattacharya" <bibhas@webagesolutions-NO-SPAM.com> wrote in message
news:bqj5nm$9kri$1@news.boulder.ibm.com...
quote:

> Default -Xmx values are too low for production. Two options exist:
>
> 1. Remove the max memory linit. Or,
> 2. Set a higher limit.
>
> --
> Bibhas Bhattacharya
> --
> Web Age Solutions Inc.
> WebSphere and WebLogic Training and Consulting Services
> www.webagesolutions.com
>
> "Peter Pontbriand" <sprocket@spam.spam.spam.storm.ca> wrote in message
> news:bp2ug1$50eu$1@news.boulder.ibm.com...
> knees
ECMessage[QUOTE][color=darkred]
or[QUOTE][color=darkred]
the[QUOTE][color=darkred]
>
>




Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com