tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aparna1 V <>
Subject Re: OutOfMemory issue
Date Tue, 01 Feb 2011 13:27:52 GMT
Hi Christopher,

Yes,  we were on jdk 1.4 and now we have moved to 1.6. 
After this, we were facing the BufferOverFlow  on this particular page so 
we increased the buffer size to 4 MB ( yes .. 4 MiB).

There is no increase in the number of users. 

The heap space is set to 128 MB, 
and Max Perm is set to 64mb. 


Christopher Schultz <>
Tomcat Users List <>
02/01/2011 03:37 AM
Re: OutOfMemory issue

Hash: SHA1


On 1/31/2011 8:42 AM, Aparna1 V wrote:
> I am facing a frequent OutOfMemoryError on the Java heap space after 
> a few hits on the application. (The page buffer for a few jsps are of 
> range 4000kb) 

4000kb is 4MiB. Is that what you meant? That's a pretty big buffer. What
do you need that big buffer for?

> The heap size for the app is 128 MB. 

Is that fixed? What are you memory settings?

> Earlier, I was using TC 4 with mssql pooling(pool.exe) without any issue 

> on a 64 MB heap size. 

Were you using an older JVM version, too? I've found that usually
everything newer needs a bit more RAM than older versions.

> Is this an issue with the server memory management or is there something 

> wrong with the configuration,
> or any other thing that i am overlooking? Please advise. 

Has anything else changed recently?

The only time we ever got OOMEs was when we had actually reached a user
threshold where we simply needed more memory to handle the traffic.
Before then, we were running with a 64MiB heap and decided to double it.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message