Dear all,
I am just reopening this thread here.
Just to give you guys some more info on this OutOfMemoryError issue.
We always see this problem on a single page. Our application uses Velocity
and in one of the pages we do some special character escaping. If you look
at the following stack trace
Dear all,
I am just reopening this thread here.
Just to give you guys some more info on this OutOfMemoryError issue.
We always see this problem on a single page. Our application uses Velocity
and in one of the pages we do some special character escaping. If you look
at the following stack
From: Steve Sheerin
Sent: Thursday, August 04, 2005 2:29 PM
To: '[EMAIL PROTECTED]'
Subject: OutOfMemoryError
I have a new Tomcat based server that is coming up with this error when
communicating with the server. Most of the time it works great, but
every now and then we get
: OutOfMemoryError
I have a new Tomcat based server that is coming up with this error when
communicating with the server. Most of the time it works great, but
every now and then we get this message. In checking the server, it's
memory looks fine - base is 1 gig, with 600 meg avail.
Any ideas
an OutOfMemoryError on the box
that looks similar to this:
java.lang.OutOfMemoryError
java.util.zip.ZipFile.open(Native Method)
java.util.zip.ZipFile.init(ZipFile.java:112)
java.util.jar.JarFile.init(JarFile.java:127)
java.util.jar.JarFile.init(JarFile.java:92
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: FW: OutOfMemoryError
WebappClassLoader.openJARs(WebappClassLoader.java:1544)
Problem is every now and then we will see an OutOfMemoryError
on the box that looks similar to this:
java.lang.OutOfMemoryError
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: 20 July 2005 17:14
To: Tomcat Users List
Subject: RE: OutOfMemoryError
WebappClassLoader.openJARs(WebappClassLoader.java:1544)
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: FW: OutOfMemoryError
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError
WebappClassLoader.openJARs(WebappClassLoader.java:1544)
Any pointers in terms of how I should approach this problem...?
I'd raise the limit on the number of open file descriptors and see what
happens.
- Chuck
: OutOfMemoryError - 100 thread limit?
the default Perm is 64M. If LeeAnn's webapp have a large number of
classes, maybe there's too many; therefore forcing the VM to resize
the perm.
IIRC (haven't looked at core HotSpot code in detail since 1.4.1 days),
the virtual address boundary between perm
should
also solve this problem.
--
Virtually,
Andre Van Klaveren
Architect III, SCP
Enterprise Transformation Services
Unisys Corporation
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 20, 2005 8:35 PM
To: Tomcat Users List
Subject: Re: OutOfMemoryError - 100 thread limit?
ok, I just tried starting tomcat with the default heap size and 18
instances of my webapp and it got OOME just as you see
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't get adjusted up when the servlets are
initializing
] wrote:
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't get adjusted up when the servlets
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:19 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get
Subject: RE: OutOfMemoryError - 100 thread limit?
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
Peter Lin reproduced and fixed the problem LeeAnn is seeing,
and said If I set my heap to -Xms256m -Xmx512m I'm able to
load the 18 webapps just fine. the total memory used after
all
to work.
peter
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
Peter Lin reproduced and fixed the problem LeeAnn is seeing,
and said If I set my heap to -Xms256m -Xmx512m I'm able
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
if it doesn't work, then back to square one :)
It would be even better to get some real data with the
-XX:+PrintGCDetails, so we can stop speculating...
- Chuck
THIS COMMUNICATION MAY CONTAIN
I, for one, am awaiting LeeAnn's response with abated breath. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL
. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit
LeeAnn's response with abated breath. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re
. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100
silly question, does this webapp have like thousands of JSP and
servlets and preload the JSP's?
peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Not a silly question :)
We have 1 servlet that is the main entry point, everything else is done
with standard java classes. We have no jsp's.
At 09:13 AM 4/21/2005, you wrote:
silly question, does this webapp have like thousands of JSP and
servlets and preload the JSP's?
peter
Possible success!
I went back to my weblogic installation which I was successfully able to
open up 25 sites to see what it was doing when starting up.
It had -XX:MaxPermSize=128m in the process description.
I added that to my catalina_opts and I got past the 18 site limitation of
just firing
glad I was wrong and you found a solution.
http://java.sun.com/docs/hotspot/VMOptions.html
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm. Atleast that's logical explanation I can think of.
21, 2005 11:21 AM
To: Tomcat Users List
Subject: Re: OutOfMemoryError - 100 thread limit?
Not a silly question :)
We have 1 servlet that is the main entry point, everything else is done
with standard java classes. We have no jsp's.
At 09:13 AM 4/21/2005, you wrote:
silly question, does
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m in the process description.
Ahah, as they say.
Can anyone give me any information on what this does? Is
this the perm gen that Chuck mentioned before?
Yes
-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 11:52 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm
:52 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m in the process description.
Ahah, as they say.
Can anyone give me any
:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm
:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm. Nothing is ever promoted
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
so it would appear by setting the PermSize, the jvm is pushing all
java.lang.Class instances to Perm rather than loading them in eden and
then promoting them to tenured.
Instances
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
so it would appear by setting the PermSize, the jvm is pushing all
java.lang.Class instances to Perm rather than loading them in eden
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
the default Perm is 64M. If LeeAnn's webapp have a large number of
classes, maybe there's too many; therefore forcing the VM to resize
the perm.
IIRC (haven't looked at core HotSpot code in detail
application.
I have added code to our servlet class which prints out the number of
active threads whenever I initialize the servlet. On Red Hat Linux
boxes, whenever we start up enough copies of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the Xms/Xmx
settings
to our servlet class which prints out the number of
active threads whenever I initialize the servlet. On Red Hat Linux
boxes, whenever we start up enough copies of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the Xms/Xmx
settings (memory profiling
. On Red Hat Linux
boxes, whenever we start up enough copies of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the Xms/Xmx
settings (memory profiling shows that we have plenty of memory
available). On Windows XP, 50 seems to be the magic number.
I have
the servlet. On Red Hat Linux
boxes, whenever we start up enough copies of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the Xms/Xmx
settings (memory profiling shows that we have plenty of memory
available). On Windows XP, 50 seems
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
This is not a memory leak in the application - we have hooked up a profiler
to the application and watched the actual memory usage when causing this
issue to happen. We have lots of memory available, are nowhere near the
Xmx limit, and the
of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the
Xms/Xmx
settings (memory profiling shows that we have plenty of memory
available). On Windows XP, 50 seems to be the magic number.
I have tried tweaking Xss parameters, my ulimit command
No, unfortunately, changing those options doesn't seem to make any
difference either.
On tomcat 3, I even tried manipulating the thread pool settings (since in 4
and 5 those are handled inside tomcat).
But I'm seeing the same problems on 3, 4 and 5.0
In fact, I can cause the error to happen
the number
of
active threads whenever I initialize the servlet. On Red Hat Linux
boxes, whenever we start up enough copies of the servlet to hit 100
active threads, we reach an OutOfMemoryError - regardless of the
Xms/Xmx
settings (memory profiling shows that we have
to
hit 100
active threads, we reach an OutOfMemoryError - regardless of the
Xms/Xmx
settings (memory profiling shows that we have plenty of memory
available). On Windows XP, 50 seems to be the magic number.
I have tried tweaking Xss parameters, my ulimit command
Perhaps this will trigger some ideas? The stack trace we get when we get
the OutOfMemoryError is :
2005-04-20 09:55:33 StandardWrapperValve[ExtraView]: Allocate exception for
servlet ExtraView
javax.servlet.ServletException: Error allocating a servlet instance
for your tests?
in other words, are you throwing 100 concurrent requests at it
simultaneously, or ramping it up over a few seconds?
peter
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
Perhaps this will trigger some ideas? The stack trace we get when we get
the OutOfMemoryError
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
Perhaps this will trigger some ideas? The stack trace we get
when we get the OutOfMemoryError is :
- Root Cause -
java.lang.OutOfMemoryError
It's what comes after this spot
, are you throwing 100 concurrent requests at it
simultaneously, or ramping it up over a few seconds?
peter
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
Perhaps this will trigger some ideas? The stack trace we get when we get
the OutOfMemoryError is :
2005-04-20 09:55:33 StandardWrapperValve
At 10:43 AM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
Perhaps this will trigger some ideas? The stack trace we get
when we get the OutOfMemoryError is :
- Root Cause -
java.lang.OutOfMemoryError
It's what
Might want to turn on -verbose:gc just to see.
I turned on verbose:gc and ran the test again:
INFO: Server startup in 14608 ms
Start Init Method.
The CONFIG_FILE from web.xml is :
WEB-INF/configuration/Configuration.properties
Using Configuration FILE:
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
This was first reported when we had multiple web applications running on
one tomcat, and a user would be logged into the site and be using the
application fine, and then if another user started working in a new site,
they would get the
the number of threads seems odd. unless your webapp creates a bunch of
threads using ServletContextListener, the total thread count should be
between 10-15. I have a webapp which creates 10 threads on startup.
When tomcat is done and my webapp is loaded, I have a total of 38.
if your webapp is
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
I turned on verbose:gc and ran the test again:
[Full GC 48357K-47096K(129792K), 0.6358540 secs]
This shows you've given the JVM only 128 MB to work with; looks like you
really are out of heap
We tried a new test :)
We added code that spins up 8 threads inside just a plain servlet that
doesn't do anything else. When I fire up 10 different instances of that
servlet, I get hundreds of threads printing out as being active - and no
out of memory errors.
So we added the same code to our
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC 47271K-47262K(129792K), 0.7056980 secs]
If anyone has any suggestions on other things that I could
check for ?
It still looks like your heap size is too small - 128MB isn't much
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC 47271K-47262K(129792K), 0.7056980 secs]
If anyone has any
-
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 20, 2005 4:35 PM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From
Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC
if your application is thread heavy, I would recommend changing it so
that one thread can manage several processes. creating 800+ threads is
going to hit a scalability and reliability wall very quickly. In
general, you want to make sure the number of threads remain constant
under constant load.
I think we've gotten things a bit confused :)
The application itself is not thread intensive - our original tests show
that each separate copy of the web application started up 3 active threads.
Further testing, when we added in debugging code that would spin up dozens
of threads just to see if
ahh ok. .. my confusion.
back to the problem you see. I've tested tomcat with 30-40 threads
without any problems in the past. Even with heavy weight JSTL tags in
JSP's, I'm able to go up to 50 threads with tomcat4.1.
I'll try hitting tomcat's status servlet with 50 threads tonight and
see what
when you say 50 threads, do you mean 50 separate web applications?
My concern right now is that we seem to be limited to 17-18 copies of our
web app on a particular installation of tomcat. And that
is just hitting the login page - not doing any work. Practically, for
applications with many
I'll try loading up 18 version of my webapp and see if tomcat blows
up. should know in a hour or so
peter
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
when you say 50 threads, do you mean 50 separate web applications?
My concern right now is that we seem to be limited to 17-18 copies
ok, I just tried starting tomcat with the default heap size and 18
instances of my webapp and it got OOME just as you see. If I set my
heap to -Xms256m -Xmx512m I'm able to load the 18 webapps just fine.
the total memory used after all the webapps are loaded is 152Megs.
the total number of
initialize the servlet. On Red Hat Linux boxes,
whenever we start up enough copies of the servlet to hit 100 active
threads, we reach an OutOfMemoryError - regardless of the Xms/Xmx settings
(memory profiling shows that we have plenty of memory available). On
Windows XP, 50 seems to be the magic
-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 6:56 PM
To: Tomcat Users List
Subject: RE: OutOfMemoryError: unable to create new native thread
Hi,
Apparently Windows NT/2000 defaults to a 1mb virtual thread stack size
per
thread unless otherwise stated
Hi,
Question: Having multiple tomcat instances on the same server - would
this
not increase the memory usage - due to multiple JVMs?
If configured correctly, the total should be just about the same. It
might be a bit higher or lower depending on the semantics of your webapp
(% in old
Greetings.
I am periodically having to restart a normally very stable tomcat 5 instance
due to:
OutOfMemoryError: unable to create new native thread
Now, as far as I understand the following are the reasons for this:
- Actually ran out of memory
- Hit max # of threads allowed to run (OS
Hi,
- Actually ran out of memory
- Hit max # of threads allowed to run (OS dependant?)
This is the most likely cause in your case, and it's OS-dependent as you
surmised. On *nix this is adjusted via the ulimit (-n) command. But on
Windows 2000 Server, I'm not sure off the top of my head.
: OutOfMemoryError: unable to create new native thread
Hi,
- Actually ran out of memory
- Hit max # of threads allowed to run (OS dependant?)
This is the most likely cause in your case, and it's OS-dependent as you
surmised. On *nix this is adjusted via the ulimit (-n) command. But on
Windows 2000
Hi,
Apparently Windows NT/2000 defaults to a 1mb virtual thread stack size
per
thread unless otherwise stated. In addition a maximum of 2gb of thread
stack space per process is allowed by Windows (not sure if this can be
changed or not!). Thus the tomcat JVM could only have 2000 odd
concurrent
already ran I
wonder what CompilerThread1 still has to do.
I've had several more crashes, all with an OutOfMemoryError in
CompilerThread1 without the Java process actually running out of heap.
I finally went back to 5.0.19 for now. I still hope there is a
possibility to fix this problem
wonder what CompilerThread1 still has to do.
I've had several more crashes, all with an OutOfMemoryError in
CompilerThread1 without the Java process actually running out of heap.
I finally went back to 5.0.19 for now. I still hope there is a
possibility to fix this problem somehow, because
Stefan Proels wrote:
Dear all,
after updating our server to Tomcat 5.0.24 last night I got 2 crashes with
the last words
Exception in thread CompilerThread1 java.lang.OutOfMemoryError:
requested 32760 bytes for ChunkPool::allocate. Out of swap space?
from Tomcat. Now the interesting is that
Dear all,
after updating our server to Tomcat 5.0.24 last night I got 2 crashes with
the last words
Exception in thread CompilerThread1 java.lang.OutOfMemoryError:
requested 32760 bytes for ChunkPool::allocate. Out of swap space?
from Tomcat. Now the interesting is that according to our GC
Guys,
I am getting java.lang.OutOfMemoryError when I start/stop/start/stop... a specific
context multiple times.
I am using Optimizeit to profile my application. I found multiple class definitions
are being held by tomcat
of same class. Everytime the context is restarted(using the Manager
Sorry I forgot to mention environment details:
WinXP 2000 professional, 256 MB RAM, 384 Page File, MySql 4, Tomcat 4.1.27
- Original Message -
From: Chandu
To: Tomcat Users List
Sent: Thursday, April 01, 2004 6:49 PM
Subject: OutOfMemoryError - Excessive class loading
Hi,
When a context is stopped, does all the resources will be released?
This
includes stopping of threads
if any and unloading of all classes which are loaded during the context
lifecycle.
No, some resources such as the classloader itself may be retained in
memory. A new one will be provided
Hi,
Use jvmstat (google it) tool to analyize it. Maybe your application memory
needs can break down Tomcat
Regards.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 15, 2004 8:18 AM
Subject: OutOfMemoryError
Hi,
I am getting the following
Hi,
I do I control it instead of viewing my memory usage?
Thank you,
Best Regards,
Uma
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I am getting the following error message when I have accessed Tomcat for
more than 2 days without shutting it down.
I am using Tomcat 5.0.19
256 MB Ram
Pentium III
Win 2k Pro
Mar 13, 2004 3:57:54 PM
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor
processChildren
you know when the OutOfMemoryError occurred?
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom
Well, I have made an assumption in most cases. The OutOfMemoryError is
logged with no timestamp to $CATALINA_HOME/logs/catalina.out. We have
a script that periodically (every 15 minutes) hits the applications and
notifies us of any error response (either status above 400 or the word
ERROR
A while back somebody mentioned that if you continuously redeploy a web
application, the symptoms you are mentioning occur. This is because of
all of the objects that are stored in the permanent generation memory.
This permanent generation runs out of space, even though the new
generation and
Hmmm...we don't do hot deploys, but the different generations are
definitely something to look at.
Thanks!
Dhruva
--- Jeff Tulley [EMAIL PROTECTED] wrote:
A while back somebody mentioned that if you continuously redeploy a
web
application, the symptoms you are mentioning occur. This is
: RE: OutOfMemoryError with Seemingly Plenty of Memory
A while back somebody mentioned that if you continuously
redeploy a web application, the symptoms you are mentioning
occur. This is because of all of the objects that are stored
in the permanent generation memory. This permanent
Do you edit the web.xml of your web application? That will cause Tomcat
to redeploy the application. We had an application that would do this
during their installation (so, only one time really), but I can imagine
an application that might be trying to dynamically deploy servlets and
set their
I am troubleshooting an issue we've been having with Tomcat 4.1.27. We
have several websites on one instance, and it regularly throws an
OutOfMemoryError, requiring a restart of Tomcat.
Some observations (warning--this is a bit long):
* The box runs two 2.8GHz Pentium 4 Hyperthreaded Xeons
hi,
I'm installed Tomcat-4.1.24 on a Linux Debian pc with j2sdk1.4.1.
On that there is an application running that causes Tomcat stoppping from
time to time.
The error I get is:
Dec 2, 2003 1:44:33 PM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception
hi,
I'm installed Tomcat-4.1.24 on a Linux Debian pc with j2sdk1.4.1.
On that there is an application running that causes Tomcat stoppping from
time to time.
The error I get is:
Dec 2, 2003 1:44:33 PM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception
Hans Steinraht wrote:
I'm installed Tomcat-4.1.24 on a Linux Debian pc with j2sdk1.4.1.
On that there is an application running that causes Tomcat stoppping from
time to time.
The error I get is:
Dec 2, 2003 1:44:33 PM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught
Christopher Schultz wrote:
So, moving on, what usually happens is that a low memory condition
triggers a GC (usually a full GC). When the GC runs, it needs some
memory to work with. If it cannot allocate memory for itself, it will
die with an OOM. If the heap hasn't increased, yet, then the GC
Howdy,
Aah. I think I see a part of the problem. First of all, the amount of
memory shown by 'ps' is completely irrelevant, except that it shows how
much memory that the OS has allocated to the Java process. This is
allowed to be more than the max heap size set for Java.
It's not completely
Howdy,
Dhruva B. Reddy wrote:
We get OutOfMemoryError's on Tomcat 4.1.27, running on RH 7.3, Sun
JDK
1.4.1_02 (with 512MB allocated to it) The box has 1GB of RAM, 2GB of
swap space, and four Xeon processors.
Can you reproduce the errors in a test environment?
Are you using the context
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: December 2, 2003 6:55 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError
Howdy,
Dhruva B. Reddy wrote:
We get OutOfMemoryError's on Tomcat 4.1.27, running on RH 7.3, Sun
JDK
1.4.1_02 (with 512MB
Trenton,
Are you using the context reloading feature? reloadable=true or
using
the tomcat manager app will cause this to happen eventually.
Really? Prove that please...
Actually, I can't prove it in his instance, but I have proved it time and time
again on ours. I'm using 4.0.4 right now
We get OutOfMemoryError's on Tomcat 4.1.27, running on RH 7.3, Sun JDK
1.4.1_02 (with 512MB allocated to it) The box has 1GB of RAM, 2GB of
swap space, and four Xeon processors.
This error seems to occur during periods of low load (like during the
Thanksgiving holiday), after which Tomcat exits.
What apps are you running ?
Maybe you are running something that consumes a lot of ram.
Dhruva B. Reddy wrote:
We get OutOfMemoryError's on Tomcat 4.1.27, running on RH 7.3, Sun JDK
1.4.1_02 (with 512MB allocated to it) The box has 1GB of RAM, 2GB of
swap space, and four Xeon processors.
This
Dhruva B. Reddy wrote:
We get OutOfMemoryError's on Tomcat 4.1.27, running on RH 7.3, Sun JDK
1.4.1_02 (with 512MB allocated to it) The box has 1GB of RAM, 2GB of
swap space, and four Xeon processors.
Are you using the context reloading feature? reloadable=true or using
the tomcat manager app
1 - 100 of 144 matches
Mail list logo
