It helped us to upgrade to java 1.5.0_10. There are fixes for memory leaks in
native memory. They do not show up in the java heap.
Ronald.
On Wed Feb 07 23:34:45 CET 2007 Tomcat Users List users@tomcat.apache.org
wrote:
http://tomcat.apache.org/faq/memory.html
If you have a lot of servlets or JSP's, you may need to increase your
permanent generation. By default, it is 64MB. Doubling it to be
-XX:MaxPermSize=256m might be a good start.
Pardon the bad math in the faq since 64*2!=256 ;)
-Tim
Nikola
| From: Tim Funk [mailto:[EMAIL PROTECTED]
| Sent: Friday, 09 February, 2007 06:30
|
| Pardon the bad math in the faq since 64*2!=256 ;)
Obviously you were thinking 64 2 -- happens to everybody... ;)
-
You have quite a bit of memory in your 'Old Generation'. You need to
determine what you're allocating that isn't being released.
Not true, see below.
Heap Usage:
PS Young Generation
Eden Space:
capacity = 10223616 (9.75MB)
used =
Given this information at the top of the jmap -heap output:
Heap Configuration:
...
PermSize = 16777216 (16.0MB)
MaxPermSize = 67108864 (64.0MB)
Doesn't this mean that I can grow to 64M of PermGen space?
I do see the capacity of
From: Sharon French [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError (but not really out of memory?)
cause tomcat processes to hang
Given this information at the top of the jmap -heap output:
Heap Configuration:
...
PermSize = 16777216
---
Version Information:
---
Red Hat Linux: 2.4.21-4.ELsmp #1 SMP i686 i686 i386 GNU/Linux
Apache: 2.0.54
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sharon,
Sharon French wrote:
Is it possible that the initial OutOfMemory error occurs when a large
garbage collection is taking place and an OutOfMemoryError is thrown
before the memory can be reclaimed
Yes. In fact, this is often when OOMs
Sharon,
You have quite a bit of memory in your 'Old Generation'. You need to
determine what you're allocating that isn't being released.
How many sessions do you have active when the problem occurs? What is your
session timeout?
What are you putting into your sessions (how much is held by
You have quite a bit of memory in your 'Old Generation'. You need to
determine
what you're allocating that isn't being released.
We have a fairly substantial amount of data that is loaded on startup and
remains for the duration. This probably accounts for part of the old-gen
usage.
I also
Hello Sharon,
just some thoughts
On 2/7/07, Sharon French [EMAIL PROTECTED] wrote:
---
Version Information:
---
Red Hat Linux:
I assume the Xms value is set to the same value as Xmx?
If not, at least earlier jdks tendered to through outofmemory
during heap resize.
I will give this a shot. Thanks.
The changes in Xmx values, did they had any impact on the duration
of the servers good state under load?
Nope.
12 matches
Mail list logo
